Re:OpenSSL Heartbleed Security Update
by grittygrease on Tuesday April 08, 2014 @02:46PM
(#7555195)
This is completely the wrong approach. Your private key might have been compromised and you're generating another certificate for the same compromised private key? What is that supposed to do?
[ Parent
| on HN ]
As discussed on twitter (https://twitter.com/grittygrease/status/453606054698692608), I should have said:
We generated new CSRs, with new private keys, but with the same dates and details as the originals. This let us get fresh certs without going through a full renewal.
Thanks for the prod.
Re:OpenSSL Heartbleed Security Update
by grittygrease on Tuesday April 08, 2014 @03:14PM
(#7555335)
Thanks for the update. Happy revocation day!
Re:OpenSSL Heartbleed Security Update
by schrodinger on Tuesday April 08, 2014 @02:48PM
(#7555204)
I think you misread... the poster said they used a new private key with the same CSR.
Re:OpenSSL Heartbleed Security Update
by grittygrease on Tuesday April 08, 2014 @02:52PM
(#7555223)
The CSR contains the public key for a unique private key. How do you have a new private key with an old CSR?