Seamonkey 2.0.13 is available, fixes security issues

[Ryan Farmer]

Binary package hint: seamonkey

Seamonkey 2.0.13 is available. Ubuntu Natty is carrying 2.0.11 which has known security vulnerabilities and bugs ranging from trivial to crashing the application.

Since 2.0.13 is stable and intended to address only bugs and security issues, I would like to request that it be considered for packaging in Natty, so as to avoid shipping software with these known problems.

For the release notes for 2.0.12 and 2.0.13 see:

http://www.seamonkey-project.org/releases/seamonkey2.0.12/
http://www.seamonkey-project.org/releases/seamonkey2.0.13/

For security issues that were fixed in these versions, see:

http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html

Short story: I think it's probably in bad taste to go forward with a version that contains a count of 7 Critical, 2 High, and 1 Moderate security vulnerabilities when the patched version is available and Natty is not frozen.

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: seamonkey (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Mon Apr 11 20:07:53 2011
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110411)
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: seamonkey
UpgradeStatus: No upgrade log present (probably fresh install)

[Chris Coulson (chrisccoulson)]

"I think it's probably in bad taste to go forward with a version that contains a count of 7 Critical, 2 High, and 1 Moderate security vulnerabilities when the patched version is available and Natty is not frozen."

Well, Natty *is* frozen now, and won't unfreeze before release.

We really need people to help out with maintaining seamonkey, as it's never top of my list of priorities.

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 743348, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.