2 ms·
There's no point implementing TLS1.2 until browsers stop silently downgrading through TLS versions under attacker control. And there's not much prospect of tha
by ctz 14y ago
There's no point implementing TLS1.2 until browsers stop silently downgrading through TLS versions under attacker control.
And there's not much prospect of that happening: it seems we're happy to exchange compatibility with less than 1% of sites for security of 100%.
- peterwwillis 14y agoFrom what i've read, it looks like the server advertises all the TLS it supports, the client picks the highest version, but then an attacker sends an RST and the client goes to the next version in the list. Is that accurate? (The only other downgrade attack I saw was on False Start which has since been disabled in Chrome) Could (or should) they support an option in the browser to require only the highest possible version of a protocol? Or is there some other fix required to mitigate the attack?