Hi,
On a friend's computer, they are getting this error when SM <2.38 tries
to perform auto-udpate. Apparently, it's a "known issue" related to SSL
certificate mismatch. See first forum post here
http://forums.mozillazine.org/viewtopic.php?f=3&t=2964365
The solution is to use admin rights to download and install a fresh copy
of the SeaMonkey distribution.
However, in this case I'd like to try to get their auto-update working
(long story) so they can get onto >2.38, and then it should be OK.
I don't fully understand the cause of the issue (client cert, server
cert, string mismatch), but I did notice some about:config values in my
own correctly updated 2.38 version.
I wonder if they change
app.update.cert.requireBuiltIn
true -> false
would it allow them to get past the error and receive the new version?
app.update.cert.requireBuiltIn;true
app.update.certs.1.commonName;aus2-community.mozilla.org
app.update.certs.1.issuerName;CN=DigiCert SHA2 Secure Server
CA,O=DigiCert Inc,C=US
app.update.certs.2.commonName;aus2-community.mozilla.org
app.update.certs.2.issuerName;CN=Thawte SSL CA,O="Thawte, Inc.",C=US
app.update.url;https://aus2-community.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
--
Gerry Hickman (London UK)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
