Hacker News Reader

Doesn't work, since rekeyed certificates are often (mostly?) backdated to have the same valid-from date as the old certificate.

I updated my key and certificate, and for the browser-visible certificate metadata only the fingerprint changed.

For all that you've heard about the disaster side, there's also a huge number of sites that weren't affected. Whitelisting wouldn't help much.

We had certs that were only used and present on machines that were not vulnerable, and therefore did not replace or revoke them. Please don't do this.

Furthermore servers that weren't even using OpenSSL or the particular version(s) that were susceptible. What is the actual percentage of servers that needed to react to this?

I dunno... Probably worth it from a netsec point of view.