Comment 86 for bug 575160

And still waiting. BTW: SeaMonkey has moved on to 2.0.11 with considerable security fixes:

<http://www.seamonkey-project.org/releases/seamonkey2.0.11/>
<http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html#seamonkey2.0.11>

Fixed in SeaMonkey 2.0.11
MFSA 2010-84 XSS hazard in multiple character encodings
MFSA 2010-83 Location bar SSL spoofing using network error page
MFSA 2010-82 Incomplete fix for CVE-2010-0179
MFSA 2010-81 Integer overflow vulnerability in NewIdArray
MFSA 2010-80 Use-after-free error with nsDOMAttribute MutationObserver
MFSA 2010-79 Java security bypass from LiveConnect loaded via data: URL meta refresh
MFSA 2010-78 Add support for OTS font sanitizer
MFSA 2010-77 Crash and remote code execution using HTML tags inside a XUL tree
MFSA 2010-76 Chrome privilege escalation with window.open and <isindex> element
MFSA 2010-75 Buffer overflow while line breaking after document.write with long string
MFSA 2010-74 Miscellaneous memory safety hazards (rv:1.9.2.13/ 1.9.1.16)

Do none of these affect Ubuntu users? Or are SeaMonkey users left to fend for themselves? SM 2.0.11 was released 10 days ago: http://www.seamonkey-project.org/news (December 9, 2010), and 2.0.11 is only showing up in Natty, an alpha system:
https://launchpad.net/ubuntu/+source/seamonkey

I've given up. I'll simply continue to install SeaMonkey directly from the seamonkey project and/or from Joe Lesko's builds:
https://launchpad.net/~seamonkey2/+archive/seamonkey2
https://launchpad.net/~seamonkey2
for as long as he'll kindly provide them.

Good luck & good night.