Bug 439372 - seamonkey 1.1.9 update
Summary: seamonkey 1.1.9 update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 8
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-28 11:28 UTC by Chris Schanzle
Modified: 2008-04-01 21:34 UTC (History)
1 user (show)

Fixed In Version: 1.1.9-1.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-01 21:32:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Schanzle 2008-03-28 11:28:32 UTC
Seamonkey 1.1.9 is released upstream with security fixes and I don't see any
released or testing packages for Fedora 8...just want to ensure someone has it
on their radar.  Thanks!

Comment 1 Kai Engert (:kaie) (inactive account) 2008-03-28 17:16:54 UTC
thanks for the ping, I'll do new builds

Comment 2 Fedora Update System 2008-03-28 19:35:24 UTC
seamonkey-1.1.9-1.fc8 has been submitted as an update for Fedora 8

Comment 3 Kai Engert (:kaie) (inactive account) 2008-03-28 20:44:18 UTC
MFSA 2008-19  XUL popup spoofing variant (cross-tab popups)
MFSA 2008-18 Java socket connection to any local port via LiveConnect
MFSA 2008-17 Privacy issue with SSL Client Authentication
MFSA 2008-16 HTTP Referrer spoofing with malformed URLs
MFSA 2008-15 Crashes with evidence of memory corruption (rv:1.8.1.13)
MFSA 2008-14 JavaScript privilege escalation and arbitrary code execution

http://www.mozilla.org/projects/security/known-vulnerabilities.html#seamonkey1.1.9

Comment 4 Fedora Update System 2008-04-01 21:32:20 UTC
seamonkey-1.1.9-1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2008-04-01 21:34:15 UTC
seamonkey-1.1.9-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.