Re:As sites move to SHA2 encryption, millions face HTTPS loc...
by eastdakota on Monday October 26, 2015 @03:38AM
(#10449994)
Not in any way we've been able to think of — and we've spent a lot of time thinking about this and running it by the crypto community. But, if someone can demonstrate such an attack and we can't fix it technically, then we will drop support for the SHA1 fallback. And, on a customer-by-customer basis, we'll allow customer to turn off fallback if they're worried about a theoretical, if undemonstrated, attack.
Re:As sites move to SHA2 encryption, millions face HTTPS loc...
by yaps8 on Monday October 26, 2015 @03:56AM
(#10450026)
Could you elaborate or do you have a source on the technique you use to mitigate downgrade attacks ?
Re:As sites move to SHA2 encryption, millions face HTTPS loc...
by ryan-c on Monday October 26, 2015 @04:02AM
(#10450038)
No mitigation is required. Part of the data signed by the server certificate in the handshake is the entire ClientHello message. If a MitM attacker did a downgrade, they would have to change the ClientHello, and then the client would notice that what the server signed does not match what they sent.
Doesn't this expose users to downgrade attack?