Remix.run Logo
▲ BoppreH 5 hours ago

> Its infrastructure was not compromised and no data was breached.

The private key of your globally trusted CA is infrastructure data and it was breached.

> All physical and logical security controls remained intact.

No, because you promised the CA Program that those keys would be HSM generated, FIPS 140-2 level 3 compliant. Ain't no compliant HSM in the world that will generate "4" as a private key.

> There were no end entity certificates issued out of the affected CA's.

I charitably read this as "revoking these weak CA didn't affect customers". But now your whole root is being revoked next week (which you forgot to mention). All your TLS customers get screwed.

Overall, good choice to give up, but lying on your way out is not a good look for a company with the tagline "Trust Delivered".

▲BubbleRings 5 hours ago | parent | next [-]

Do you think they left because they figure they’d never get enough trust back to make it worth trying?

▲stephbook 2 hours ago | parent [-]

If you issue certificates for a Google domain, Google will kill you.

As in, Chrome will distrust your CA and your business is dead. I think that's reasonable.

▲Cyphus 5 hours ago | parent | prev | next [-]

“Trust, Liberated”

▲WebDanube 5 hours ago | parent | prev [-]

[dead]