3 ms·
Mozilla was much more forceful when they removed a CA from their default certificate list earlier this year, for lacking in their audits[1], when the post indic
by icebraining 11y ago
Mozilla was much more forceful when they removed a CA from their default certificate list earlier this year, for lacking in their audits[1], when the post indicates no suspicion of wrong certificate emission.
Compared to that, Google just forcing Symantec to be externally audited after it was shown that, not only have they issued wrong certificates, but also that they are unable to properly audit themselves, is being soft on them.
[1] https://blog.mozilla.org/security/2015/04/27/removing-e-guven-ca-certificate/ https://blog.mozilla.org/security/2015/04/27/removing-e-guve...
- dlgeek 11y agoI think that's less about the browser vendor and more about the CA. The Symantec CAs are the most widely used on the internet (They bought Verisign's CA business and roots) and are used on 4 of the Alexa Top 10 websites (so I'd assume a similar percentage of the rest). If a browser vendor just kicked them out, users would abandon that browser - just imagine if 40% of your common websites stopped working.
- pilif 11y agoI was thinking about this. They could special-case it to not allow any certificates issued past some cutoff-date. This way the existing internet continues to work but who is going to renew a certificate, knowing it's not going to work in the browser with the biggest market share?