Re: Auto-Update "Something is trying to trick SeaMonkey..."
Paul B. Gallagher wrote: My recollection is 2.35, but either way, the point is you have to install one update manually to get past the certificate issue, and from then on auto updates will work again. I was able to visit over the holidays, and the new SM is now installed and working. It turns out that it could have been done without admin rights anyway; I must have originally installed it "per user" and that's why the updates had been working for over five years. -- Gerry Hickman (London UK) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto-Update "Something is trying to trick SeaMonkey..."
Edmund Wong wrote: Gerry Hickman wrote: Hi, 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? The basic issue is that around 2.38b1 (iirc), we had changed certs, so anything < 2.38b1 won't be able to upgrade to the latest version and will require a full download and install. So while 2.38 -> 2.39 works, 2.x -> 2.38+ (where x <38) won't update. My recollection is 2.35, but either way, the point is you have to install one update manually to get past the certificate issue, and from then on auto updates will work again. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto-Update "Something is trying to trick SeaMonkey..."
Gerry Hickman wrote: > Hi, > > 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? The basic issue is that around 2.38b1 (iirc), we had changed certs, so anything < 2.38b1 won't be able to upgrade to the latest version and will require a full download and install. So while 2.38 -> 2.39 works, 2.x -> 2.38+ (where x <38) won't update. Edmund ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Auto-Update "Something is trying to trick SeaMonkey..."
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=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 support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
