+++ This bug was initially created as a clone of Bug #541316 +++ Tracking seamonkey here # Ebuilds for firefox{,-bin}-{31.5,36} and thunderbird{,-bin}-31.5 are in the tree. Stabilization can occur for firefox{,-bin}-31.5 and thunderbird{,-bin}-31.5 at any time. I will CC arches properly once at a regular computer, if someone else doesn't do it beforehand. Please note that seamonkey{,-bin} is also vulnerable but the fixed release hasn't been..uhm..released. # https://www.mozilla.org/en-US/security/advisories/mfsa2015-11/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-12/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-13/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-14/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-15/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-16/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-17/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-18/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-19/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-20/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-21/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-22/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-23/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-24/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-25/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-26/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-27/
+*seamonkey-2.33 (11 Mar 2015) + + 11 Mar 2015; Lars Wendler <polynomial-c@gentoo.org> + -seamonkey-2.31-r1.ebuild, +seamonkey-2.33.ebuild: + Version bump. Removed old. + This relaese should address all mentioned issues.
For the record, seamonkey{,-bin}.2.33.1 have already bee stablilized quite a while ago. So all what is necessary here is to decide if we want to send out a GLSA.
So added to an existing GLSA, will send out with the next Mozilla products GLSA
This issue was resolved and addressed in GLSA 201701-15 at https://security.gentoo.org/glsa/201701-15 by GLSA coordinator Thomas Deutschmann (whissi).
SeaMonkey was removed from the GLSA.
This issue was resolved and addressed in GLSA 201701-35 at https://security.gentoo.org/glsa/201701-35 by GLSA coordinator Aaron Bauman (b-man).