3 ms·
This sounds really bad. Is it? So, if a server is accepting sslv2 at all, then all connection (including TLS connections) to the same server are practically co
by DenisM 11y ago
This sounds really bad. Is it?
So, if a server is accepting sslv2 at all, then all connection (including TLS connections) to the same server are practically compromised. That is, assuming both sslv2 and TLS use the same key. Therefore, having allowed sslv2 in the past would only jeopardize clients foolish enough to use it, but now it endangers every single client. Is that right?
Two very important things come form that:
Everyone who had sslv2 enabled at any point in the past must get a new SSL certificate right away. Right?
Windows XP has TLS disabled by default, which in practice means unavailable. So we must cut them off. Therefore Windows XP is dead-dead, starting today. Right?
- pfg 11y ago> Everyone who had sslv2 enabled at any point in the past must get a new SSL certificate right away. Right? No, unlike Heartbleed, the key isn't leaked directly. Revocation and generating a new key isn't necessary - just patch your stuff and disable SSLv2. > Windows XP has TLS disabled by default, which in practice means unavailable. So we must cut them off. Therefore Windows XP is dead-dead, starting today. Right? IIRC XP supports TLS 1.0.
- DenisM 11y agoIt does support TLS, but it's disabled out of the box, and no one who is still running XP is likely to turn it on.
- pfg 11y agoThat seems to be the case only for IE 6, not 7 or 8[1] (which are available on XP). [1]: https://en.wikipedia.org/wiki/Template:TLS/SSL_support_history_of_web_browsers https://en.wikipedia.org/wiki/Template:TLS/SSL_support_histo...
- DenisM 11y agoThanks for rescuing me from my own ignorance! I was reading a different chart that wasn't as clear.
- DenisM 11y agoAh so it's not exfiltratimg the key, it uses sslv2 oracle to break captured TLS traffic. Ok, that makes it a lot less scary. Pretty bad still, but least the keys are not compromised.
- yuhong 11y agoOnly if they are using IE6 I think. That being said, I think there are some IE7 and IE8 upgrades that inherits the old default from IE6.
- mcpherrinm 11y agoNote that there's an SSLv3 after SSLv2 -- both are broken, but SSLv2 is just a much bigger liability than before. SSLv3 is also broken. You shouldn't have had SSLv2 enabled for many years now. If you need SSLv3 for WinXP support, this bug doesn't change anything in that regard.
- DenisM 11y agoGood point on v3. I kept v2 running because we couldn't bring ourselves to prevent connections from clients of our clients, it's not our place to tell them what to do, especially if it only harms them and no one else. This time it harms everyone, including high-privilege users, so it's a lot easier to justify.