Let's talk Browsers...

quote:

---

With Google Chrome shitting the bed recently with SSL

---

Got a link? I haven't heard anything.

I wonder if he's talking about this.

quote:

---

Chrome 45, Firefox 40 and Opera 30 have all started to block HTTPS connections to servers using 512-bit Diffie-Hellman key exchange. The reason is that back in May a group of computer scientists discovered an attack that makes any TLS connection downgrade to 512 bits which can then be cracked in a reasonable time. LOGJAM - Can The NSA Break 1024-bit DHM Keys?

Put simply, a 512-bit key is not secure against a serious attack. At the moment it is estimated that it would take a 24-core machine 90 seconds to crack such a key. Moving up to 1024 bits changes the problem to something that needs 45M core years - which is supposed to be within the reach of state agencies.

As a response Google, Mozilla and Opera have modified their browsers to detect when 512-bit key TLS connections are possible with a server. However, and this is where the problems begin, rather than simply warning the user, all three browsers simply refuse to go any further until the problem is corrected on the server.

---

LINK

Although that seems more like sites and ssl certificiate suppliers dropping the ball. I know I got warned about a year in advance to reinstall some certs that needed upgrading. If I don't upgrade them I wouldn't blame the browsers when it breaks.

Bewbz

quote:

---

Although that seems more like sites and ssl certificiate suppliers dropping the ball. I know I got warned about a year in advance to reinstall some certs that needed upgrading. If I don't upgrade them I wouldn't blame the browsers when it breaks.

---

Agreed - I actually applaud Google for that. Better levels of security are good for all, even if forced.