News for hackers. Stuff that matters.

adef

Re:Chrome/Firefox aren't checking CA revocation lists on Wednesday April 09, 2014 @05:38AM (#7558418)
Then we should just all agree to treat certificates issued before 08/04/2014 to be invalid for everyone. It will be a day or two of complete mess but given the scale of the exploit it is not crazy to consider every single certificate used before this date to be insecure. And this way we don't rely on broken revocation mechanism. And it will force sys admins to follow good practice (for instance, the public lab I work for still have not fixed the heartbleed bug on our central auth server and they are not yet convinced it is necessary to regenerate the certificates...).

Ask HN: Any plan to prevent connection to heartbleed vulnerable site by default?

It would be nice if my web browser would prevent me from going on any site with a vulnerable version of OpenSSL, the same way a warning is displayed when a certificate is not valid as it would prevent people from thinking their connection is secured while it is absolutely not. Also, it would be nice to prevent connection to any site with a certificate that was not generated after the exploit...

( Read More... | 1 comment | 2 points | on HN )