This bug was fixed in the package seamonkey - 2.0.13+nobinonly-0ubuntu1
--------------- seamonkey (2.0.13+nobinonly-0ubuntu1) natty; urgency=low
* New upstream release v2.0.13 (SEAMONKEY_2_0_13_RELEASE)
* SECURITY UPDATE: MFSA-2011-11: Several fraudulent HTTPS certificates were placed on the certificate blacklist to prevent their misuse. These could allow an attacker to perform a man-in-the-middle attack. (LP: #743348) - http://www.mozilla.org/security/announce/2011/mfsa2011-11.html * SECURITY UPDATE (2.0.12): - http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html#seamonkey2.0.12 -- Micah Gersten <email address hidden> Tue, 12 Apr 2011 15:26:18 -0500
This bug was fixed in the package seamonkey - 2.0.13+ nobinonly- 0ubuntu1
--------------- nobinonly- 0ubuntu1) natty; urgency=low
seamonkey (2.0.13+
* New upstream release v2.0.13 (SEAMONKEY_ 2_0_13_ RELEASE)
* SECURITY UPDATE: www.mozilla. org/security/ announce/ 2011/mfsa2011- 11.html www.mozilla. org/security/ known-vulnerabi lities/ seamonkey20. html#seamonkey2 .0.12
MFSA-2011-11: Several fraudulent HTTPS certificates were placed on the
certificate blacklist to prevent their misuse. These could allow an
attacker to perform a man-in-the-middle attack. (LP: #743348)
- http://
* SECURITY UPDATE (2.0.12):
- http://
-- Micah Gersten <email address hidden> Tue, 12 Apr 2011 15:26:18 -0500