3 ms·
To clarify trustico disclosed private keys to an entity other than the owner of the key, which automatically starts a 24 hour countdown for the CA. regardless
by olliej 9y ago
To clarify trustico disclosed private keys to an entity other than the owner of the key, which automatically starts a 24 hour countdown for the CA.
regardless of who discloses the private key, a CA is required to revoke any keys that they learn have been compromised within 24 hours. CAs have been reprimanded in the past for failing to do so.
The only ambiguity is the initial request to revoke by trustico - essentially for a CA the question is whether trustico is the agent for the certificatesTo clarify they disclosed private keys to an entity other than the owner of the key, which automatically starts a 24 hour countdown for the CA.
The only ambiguity here is whether a reseller like trustico gets to decide to revoke certificates that they sold or whether the end users are the owner and so are the only people who can request revocation without proof of key compromise.
From the point of view of the CA the initial “revoke all these certs “ email could have been any random person on the internet collecting public certificates, and then telling the CA to revoke them.
The communication that needlessly included the private keys was equivalent to someone trawling github or what have you, then reporting all private keys that they found to the appropriate CA. It doesn’t matter how someone proves access to the private key, and it doesn’t matter who demonstrates it, all that matters is that someone said “here is evidence this key is no longer under complete control by its owner”.
At that point a CA must revoke and no one gets to stop that.