3 ms·
I don't think Mozilla tried to protect the CA. I think Mozilla tried to protect their own browser, by tacitly releasing updates for blacklisting those certific
by bad_user 16y ago
I don't think Mozilla tried to protect the CA.
I think Mozilla tried to protect their own browser, by tacitly releasing updates for blacklisting those certificates, with the rationale being that this way Mozilla updates wouldn't also get blocked.
As the article says, those certificates have value in a tightly controlled network, because otherwise the browser would get a revocation status for that certificate using the OCSP protocol. In such a network it would also be feasible to also block Mozilla updates, and making the issue public wouldn't have helped (from this perspective).
Not saying that what they did was OK, but the issue is not so cut and dry.
- trotsky 16y agoAccording to the Mozilla ticket on the issue, Mozilla did not disclose because Comodo asked them not to. While the stated motivation of a coordinated disclosure sounds decent enough, it's hard to believe it was really in either Mozilla's or their user's best interests. Microsoft was the last to patch, and I think if you're dealing with an attacker that would shut off microsoft.com (even selectively) or WU you're probably well beyond an RA compromise. https://bugzilla.mozilla.org/show_bug.cgi?id=643056#c20 https://bugzilla.mozilla.org/show_bug.cgi?id=643056#c20 It seems to me that there is a bit of a question (at least in a few people's minds) if there was going to be any kind of disclosure if Jacob didn't come along.