SeaMonkey 2.3

Discussion about Seamonkey builds
User avatar
ElTxolo
Posts: 2811
Joined: July 30th, 2007, 9:35 am
Location: Localhost

Re: SeaMonkey 2.3 ßeta 3

Post by ElTxolo »

SeaMonkey 2.3 is officially (August 16, 2011') released! =D>
How to Ask Questions The Smart Way - How to Report Bugs Effectively ;)
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20240318 SeaMonkey/2.53.18.2
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20240416 SeaMonkey/2.53.19 :lildevil:

~
User avatar
therube
Posts: 21714
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: SeaMonkey 2.3

Post by therube »

:-).
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
rsx11m
Moderator
Posts: 14404
Joined: May 3rd, 2007, 7:40 am
Location: US

Re: SeaMonkey 2.3

Post by rsx11m »

Just popped up... bug 679705, Tracking bug for build and release of SeaMonkey 2.3.1. That's likely a chemspill release... :-(
User avatar
Philip Chee
Posts: 6475
Joined: March 1st, 2005, 3:03 pm
Contact:

Re: SeaMonkey 2.3

Post by Philip Chee »

rsx11m wrote:Just popped up... bug 679705, Tracking bug for build and release of SeaMonkey 2.3.1. That's likely a chemspill release... :-(

Nope. No security problem. Just a bug that will prevent SeaMonkey from updating in future (need to change a pref to point to the new CA certificate). Otherwise users will be stuck with whatever version they are on (unless they download a new version manually).

Phil
rsx11m
Moderator
Posts: 14404
Joined: May 3rd, 2007, 7:40 am
Location: US

Re: SeaMonkey 2.3

Post by rsx11m »

Thanks, so people who already updated from 2.2 to 2.3 won't be able to update to 2.3.1 from AUS once it's out?
User avatar
Philip Chee
Posts: 6475
Joined: March 1st, 2005, 3:03 pm
Contact:

Re: SeaMonkey 2.3

Post by Philip Chee »

rsx11m wrote:Thanks, so people who already updated from 2.2 to 2.3 won't be able to update to 2.3.1 from AUS once it's out?

People who are now on 2.3 won't be able to auto-update to 2.x (where x>3) if they:
1. Don't upgrade to 2.3.1 within the next 40 days (well 39 days). or
2. Add a pref to about:config manually.

Phil
User avatar
Philip Chee
Posts: 6475
Joined: March 1st, 2005, 3:03 pm
Contact:

Re: SeaMonkey 2.3

Post by Philip Chee »

FYI: http://hg.mozilla.org/comm-central/rev/ff7b4aaace25

Code: Select all

     1.1 --- a/suite/browser/browser-prefs.js
     1.2 +++ b/suite/browser/browser-prefs.js
     1.3 @@ -510,16 +510,20 @@ pref("app.update.cert.maxErrors", 5);
     1.4  // 2. the preference name must exist as an attribute name on the certificate and
     1.5  //    the value for the name must be the same as the value for the attribute
     1.6  //    name on the certificate.
     1.7  // If these conditions aren't met it will be treated the same as when there is
     1.8  // no update available. This validation will not be performed when using the
     1.9  // |app.update.url.override| preference for update checking.
    1.10  pref("app.update.certs.1.issuerName", "OU=Equifax Secure Certificate Authority,O=Equifax,C=US");
    1.11  pref("app.update.certs.1.commonName", "aus2-community.mozilla.org");
    1.12 +pref("app.update.certs.2.issuerName", "CN=GeoTrust SSL CA,O=\"GeoTrust, Inc.\",C=US");
    1.13 +pref("app.update.certs.2.commonName", "aus2-community.mozilla.org");
    1.14 +pref("app.update.certs.3.issuerName", "CN=Thawte SSL CA,O=\"Thawte, Inc.\",C=US");
    1.15 +pref("app.update.certs.3.commonName", "aus2-community.mozilla.org");
    1.16 
    1.17  // Interval: Time between checks for a new version (in seconds)
    1.18  //           default=1 day
    1.19  pref("app.update.interval", 86400);
    1.20  // The minimum delay in seconds for the timer to fire.
    1.21  // default=2 minutes
    1.22  pref("app.update.timerMinimumDelay", 120);
    1.23  // Give the user x seconds to react before showing the big UI. default=12 hrs

Phil
Post Reply