For those of you who are reading this and on a SeaMonkey version 2.1 through 2.3.0 you will be unable to currently update your version of SeaMonkey through automated means. (SeaMonkey 2.0.x did not have this update security measure, so is unaffected)
WHY:
Our secure certificate for updates, used to protect you, our users, from fraud and issues with the update had to be changed. The one we had expired and we were unable to renew it with the same information we baked into SeaMonkey by default.
WHAT:
We fixed this issue in our version 2.3.1, so if you have that version or newer you will not be affected. And no need to worry.
WORKAROUND:
You can manually install a new version from our website at www.seamonkey-project.org. Or apply our hotfix
HOTFIX AVAILABLE:
I have created a hotfix addon you can install into your SeaMonkey to once again update to a newer version of SeaMonkey via our internal update mechanics. This hotfix currently requires a restart of SeaMonkey, though I do plan to update it in the future to be a “restartless” addon for the versions I am able to.
NOTES:
This is different than a confusing error that gets reported in versions from 2.3.1 and newer that indicates the update server is a wrong certificate. This error is reported whenever we check against our builtin list, and of course it finds the first one we have listed as incorrect and reports it. The next cert in line is found to be ok. So this error ends up being a false positive.
-
Recent Posts
Recent Comments
- H. on SeaMonkey 2.53.18.2 is out!
- Thorben on SeaMonkey 2.53.18.2 is out!
- xrror on SeaMonkey 2.53.18.2 is out!
- Wolpi on SeaMonkey 2.53.18.1 updates
- Augusto on Teething problems with archives
Archives
- September 2024
- July 2024
- March 2024
- January 2024
- December 2023
- November 2023
- September 2023
- August 2023
- July 2023
- March 2023
- January 2023
- December 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- April 2021
- March 2021
- January 2021
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- February 2020
- January 2020
- December 2019
- September 2019
- August 2019
- July 2019
- February 2019
- January 2019
- December 2018
- September 2018
- July 2018
- May 2018
- April 2018
- February 2018
- November 2017
- October 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- December 2016
- October 2016
- September 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- April 2015
- August 2014
- November 2012
- October 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- October 2011
- September 2011
- August 2011
- June 2011
- April 2011
- March 2011
- February 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- July 2009
- June 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- April 2006
- February 2006
- January 2006
- December 2005
- November 2005
- September 2005
Categories
Meta
Hi, we should use this blog to report news from the SeaMonkey universe, users should stay in touch with the SeaMonkey Team.