Bug 577290

Summary: seamonkey 2.x for F11? unresolved security issues in 1.x
Product: [Fedora] Fedora Reporter: long
Component: seamonkeyAssignee: Martin Stransky <stransky>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: caillon, gecko-bugs-nobody, kengert, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: seamonkey-1.1.19-1.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-21 21:53:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description long 2010-03-26 16:07:46 UTC
Description of problem:
Just wondering when we will be getting seamonkey 2.x for F11?  As stated on http://www.seamonkey-project.org/ "For the few who can't afford that, a last 1.x release that does fix a few, but not all security issues, is available as SeaMonkey 1.1.19."

Version-Release number of selected component (if applicable):
seamonkey-1.1.18-1.fc11.x86_64

How reproducible:
n/a

Steps to Reproduce:
1. n/a
2.
3.
  
Actual results:
n/a

Expected results:
n/a

Additional info:

Comment 1 long 2010-04-20 17:12:03 UTC
*chirp* *chirp* *chirp*

anyone here?

Comment 2 Martin Stransky 2010-04-20 19:51:29 UTC
Uff, okay, adding to queue.

Comment 4 Fedora Update System 2010-04-21 10:41:50 UTC
seamonkey-1.1.19-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/seamonkey-1.1.19-1.fc11

Comment 5 Fedora Update System 2010-04-21 21:53:21 UTC
seamonkey-1.1.19-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 long 2010-04-22 19:29:17 UTC
Thanks, and sorry for being a PITA but I'm wondering if the security issues that were not fixed in 1.1.19 are anything to be worried about (e.g. remote code execution).