The list of known vulnerabilities hasn't been updated for SeaMonkey 2.40 yet, but it should contain at least all core fixes up to Firefox 43.0.
Note: There are still issues with the automated updates. If you are on an older version and don't get an update offered even with Help > Check for Updates, please download a fresh installer from http://www.seamonkey-project.org/ and run it to install 2.40 from scratch. All of your setting and messages should not be affected.
Last edited by rsx11m on March 19th, 2016, 2:51 pm, edited 1 time in total.
Reason:added instructions for manual update
After so long a delay, for which we apologize, the SeaMonkey
Project is pleased to announce the release of SeaMonkey 2.40!
Please note that the website information, while updated for
2.40, still requires a bit more work.
We cannot repeat this enough. Thank you everyone for your
patience with us. This very long delay due to infrastructure
and resource issues has been very trying on a lot of people.
It has been a very tough release. I think it's the
toughest one I've done. However, this isn't to say that
I did this alone. Kudos go to a lot of people, particularly
the guys/gals in Mozilla's IT and RelEng dept.
I particularly want to thank Nick Thomas for his sheer
brilliant idea that helped me unhork the partial mar upload
script as well as pointing out the necessary changes
to migrate off FTP to S3.
Thanks to Jens Hatlak for taking the time to do the Website
patch. (Really, sorry for the delay.)
Also, thanks to Justin Wood for giving me this opportunity
to work out the problems myself. If you all take a look
at bug 1233615, I think I rivaled the mess I did with
the GTK bug (conveniently forgotten the # ). The
repo changes I made... oh boy. Only time will heal
the mess^H^H^H^H wounds. ;P
Anyway, most of all, thanks to all the users out there
for hanging on to this project. The words of encouragement
(especially during the broken-hand period) definitely gave
me a boost of energy.
Oh. Before I forget and in the light of being transparent,
there is a chance I might have goofed something up, especially
during the 2.39 Win32 builds as well as the 2.40 builds and
also the partial mar and complete mar updates. I hope I
didn't screw things up too much, if at all (here's hoping).
Please do post here on your findings.
Fire 750, bring back 250. Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Addendum for OpenSUSE users: They have published 2.40 in their distros for quite a while already. Since they ship certain core libraries like NSS and NSPR as separate packages, SeaMonkey benefits from the most recent Firefox update, using NSS 3.21.1 rather than 3.20.1 and NSPR 4.12 rather than 4.10.10; this means that a couple of additional security fixes from those libraries (e.g., MFSA 2015-150, MFSA 2016-07, MFSA 2016-35) should be covered already in SM 2.40 ahead of the 2.42 release.
You can check the current version of those libraries at the bottom of the Help > Troubleshooting page.
Driving along as fast as ever in tahrpup 6.0.5 - original pet a few versions ago from official repo, no package tweaks.
No problems applying the update.
rsx11m wrote:.... Since they ship certain core libraries like NSS and NSPR as separate packages, SeaMonkey benefits from the most recent Firefox update, using NSS 3.21.1 rather than 3.20.1 and NSPR 4.12 rather than 4.10.10; this means that a couple of additional security fixes from those libraries (e.g., MFSA 2015-150, MFSA 2016-07, MFSA 2016-35) should be covered already in SM 2.40 ahead of the 2.42 release.
You can check the current version of those libraries at the bottom of the Help > Troubleshooting page.
NSS 3.22.1 & NSPR 4.12 in SeaMonkey 2.40x86_64Archlinux
It has been a decent 5-days since version 2.40 has released.
However, my version 2.39 is still not getting any indication that version 2.40 is available. When using the "Check for Updates" menu feature it continues to say that there are no updates.
Have the issues with the download server and auto-updating functions been resolved as yet?
Should I just download the version as linked here (and elsewhere) and install it over my current version 2.39? I don't want to loose anything.
I'm running Windows 10-64 bit - latest updates in place.
Any other software offering updates are coming through OK so it's not an AV issue.
Seems that the issue with autoupdate is not resolved yet, so just download the full installer and run it - you will not lose anything.
I did that several times in the past, I did that for 2.39 -> 2.40 and I'm still alive
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
). The
.
