News for hackers. Stuff that matters.
Re:How not to run a CA by edaemon on Thursday March 01, 2018 @01:08PM (#16494485)
You don't need the private keys for revocation, and you're right that compromise of the private key is one of the best reasons to revoke a cert.

I can't figure out why the Trustico CEO emailed the private keys to DigiCert. It doesn't make sense.

Re:How not to run a CA by wcoenen on Thursday March 01, 2018 @04:36PM (#16496600)
The Trustico CEO intentionally compromised the private keys to force DigiCert to revoke the certificates. DigiCert wouldn't do this otherwise on his request; it's the actual owner of the certificate who needs to request revocation.
Re:How not to run a CA by edaemon on Thursday March 01, 2018 @04:53PM (#16496736)
I meant I don't get why he would want to do that. Why insist that all of his customers' keys be revoked? Why intentionally compromise the keys to make that happen?

After reading more about it, though, I think it's less that it doesn't make sense and more that the person making these decisions is incompetent.

Re:How not to run a CA by MertsA on Friday March 02, 2018 @08:33AM (#16501208)
In fairness, all of those private keys were already compromised from the start. I have no clue why the CEO decided to take such harmful action to his own company, but one way or another all of those certificates needed to be reissued.