(In reply to Ioana Budnar [QA] from comment #115)
Verified on the 20120305181207 builds:
Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20100101 Firefox/11.0
Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20100101
(In reply to Wan-Teh Chang from comment #14)
Comment on attachment 557158
Patch (v1)
// By request of the Dutch government
I suggest this comment be reworded. This comment
implies we yielded to government pressure. I doubt
that's the case.
Can someone please blog on the Mozilla
Presumably comment 8 can be morphed into a test, either automated or
Litmus, or both. Setting flags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741528
Title:
Compromised Comodo SSL certificates
(In reply to comment #97)
Yeah, we should be able to test this through automation.
This should bear bug 617414 in mind. I don't know how SSL tests are
currently performed and whether you'd need a couple more certificates
from Comodo (one to blacklist and one to not) as this code is only run
if
Resetting the Litmus flag to indicate that the test still exists in
Litmus (and I think it should until it is replaced, or until it is no
longer a valid test as per comment 93). Given that this is a security
issue, surely a Litmus test is better in the interim? Let me know if I'm
wrong.
--
You
(In reply to comment #69)
Created attachment 520887 [details]
fix a leak
This was landed as part of bug 644012.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741528
Title:
Compromised Comodo SSL
