7 ms·
> What is the minimum failure of any CA required for me to get popped? They need to issue an intermediate with this weird constraint, for most CAs that's a maj
by tialaramex 4y ago
> What is the minimum failure of any CA required for me to get popped?
They need to issue an intermediate with this weird constraint, for most CAs that's a major business decision, maybe bringing in auditors to witness the ceremony, and then it's advertised, which seems like we'd go "Er, why does it have this really strange constraint" and the jig is up.
> Do you know every CA your OS and each browser trusts out of the box?
Yes.
> Have you done an audit of each one of them? Does an audit 100% prevent a breach from happening in the future?
No, I have not performed an audit of any public CAs. My observation, over years more and less actively overseeing the Web PKI (sometimes as a contributor to m.s.d.policy) is that the CAs are on the whole not malevolent but they're sometimes incompetent and lazy, like most humans.
I think you're imagining this is an end entity certificate needed, but the end entity certificate isn't interesting here, OpenSSL is (mis)parsing data from an intermediate, the end entity certificate is just a trigger and not an interesting one. I don't see any way you could get such a "trigger" certificate from Let's Encrypt, but I wouldn't expect it's hard to buy something suitable from a for-profit CA, however the problem is that there's no malformed intermediate to act as the explosive for you to detonate.