Re:Many sites reusing Heartbleed-compromised private keys
by mikeash on Wednesday May 14, 2014 @12:25PM
(#7744561)
I think that "no word about the keys" is simply due to a huge gulf in understanding. To the people giving out the advice, it's obvious that "reissue your certificates" implies "with a new private key", so obvious that they can't even imagine someone doing otherwise. It's easy to skip out on the basics that you're sure "everyone knows".
Re:Many sites reusing Heartbleed-compromised private keys
by higherpurpose on Wednesday May 14, 2014 @08:36AM
(#7743347)
Maybe they should just be advised to use PFS/ECDHE instead (which should be done anyway), and it would solve this problem by itself.
Re:Many sites reusing Heartbleed-compromised private keys
by sdevlin on Wednesday May 14, 2014 @08:41AM
(#7743372)
That would not solve the problem of active man-in-the-middle attacks.
Re:Many sites reusing Heartbleed-compromised private keys
by mobiplayer on Wednesday May 14, 2014 @08:58AM
(#7743437)
Yes, even renewing your keys and certs doesn't mean any previous communication is not compromised :)
The problem is that many people in the industry doesn't really understand the basics. How come is there a leak of your certificate, if that's the public key you're showing to every single client that connects to your SSL enabled site?
I've even seen sysads advising on forums about reissuing certs after Heartbleed, but no word about the keys.