8 ms·
What's happening at the moment is that Mozilla (and Google) are undertaking fact-finding to figure out how badly WoSign messed up and to explore possible penalt
by jcranmer 10y ago
What's happening at the moment is that Mozilla (and Google) are undertaking fact-finding to figure out how badly WoSign messed up and to explore possible penalties. Removing WoSign, or even actively distrusting the certificate, is certainly on the table. As others have pointed out, there are now more remedies available than merely pulling the CA.
That said, when you read the email thread, it's abundantly clear that WoSign is not saying what they should be saying. The first response document is inadequate (although they're working on a second document in response to the extra incidents): it seems like WoSign is trying to say "we quickly fixed every instance brought up to us!" and they aren't understanding that said answer isn't good enough for such a serious breach of trust. The remedy at this point is likely to be at least as severe as forbidding any certificate with an issuedBefore of soon. Honestly, if you're a sysadmin using a WoSign cert, I would recommend immediately looking into obtaining a cert from another CA as a backup.