Re: V2.48 Security Certificate Problem

Thanks for the idea. I'll give it a try. Paul B. Gallagher wrote: Henrik37 wrote: Thanks so much for your comment.  I am going to test both of your ideas. However, see my response to Mr. Grahl and Mr. Ross on how I got Windows Update 'more or less' working again. I also had trouble with

Re: V2.48 Security Certificate Problem

Henrik37 wrote: Thanks so much for your comment. I am going to test both of your ideas. However, see my response to Mr. Grahl and Mr. Ross on how I got Windows Update 'more or less' working again. I also had trouble with WU failing on Win7 in December, saying something about the service not

Re: V2.48 Security Certificate Problem

Thanks so much for your comment. I am going to test both of your ideas. However, see my response to Mr. Grahl and Mr. Ross on how I got Windows Update 'more or less' working again. Lee wrote: On 1/28/18, Henrik37 via support-seamonkey wrote: Henrik37

Re: V2.48 Security Certificate Problem

Mr. Grahl and Mr. Ross: Thanks so much for your comments. Subsequent to sending the note you both referenced, I read somewhere that someone at Microsoft had incorrectly changed the date on something to do with Windows Update on Win 7 and a solution was to change the date on my PC to something

Re: V2.48 Security Certificate Problem

On 1/28/2018 4:35 PM, Henrik37 wrote: Henrik37 wrote: Since updating my Kaspersky Total Internet software to the 2017 version. SM 2.48 is reporting lots of security certificate errors. Is this likely to be because SM 2.48 needs updating, a Kaspersky problem, or something else? Thanks, in

Re: V2.48 Security Certificate Problem

On 1/28/18, Henrik37 via support-seamonkey wrote: > Henrik37 wrote: >> Since updating my Kaspersky Total Internet software to the 2017 version. >> SM 2.48 is reporting lots of security certificate errors. >> >> Is this likely to be because SM 2.48 needs

Re: V2.48 Security Certificate Problem

Same for SeaMonkey: https://support.kaspersky.com/general/error/13529 FRG David E. Ross wrote: On 1/28/2018 2:35 PM, Henrik37 wrote: Henrik37 wrote: Since updating my Kaspersky Total Internet software to the 2017 version. SM 2.48 is reporting lots of security certificate errors. Is this

Re: V2.48 Security Certificate Problem

On 1/28/2018 2:35 PM, Henrik37 wrote: > Henrik37 wrote: >> Since updating my Kaspersky Total Internet software to the 2017 version. >> SM 2.48 is reporting lots of security certificate errors. >> >> Is this likely to be because SM 2.48 needs updating, a Kaspersky >> problem, or something else?

Re: V2.48 Security Certificate Problem

Henrik37 wrote: Since updating my Kaspersky Total Internet software to the 2017 version. SM 2.48 is reporting lots of security certificate errors. Is this likely to be because SM 2.48 needs updating, a Kaspersky problem, or something else? Thanks, in advance, for advice, fix suggestions,

Re: V2.48 Security Certificate Problem

How to enable or disable secure connections (HTTPS) check https://support.kaspersky.com/13558#block3 FRG Henrik37 wrote: David E. Ross wrote: On 12/18/2017 1:17 PM, Henrik37 wrote: Oops - after a complete reboot, SM 2.49.1 does appear to have solved the problem. Does anyone have any idea

Re: V2.48 Security Certificate Problem

Kapersky is intercepting https traffic. You either need to disable this or import the Kapersky certificate into SeaMonkey. I am not using Kapersky and would never allow this to happen anyway so I can't help you with locating the certificate. It is essentially a Kapersky problem because the

Re: V2.48 Security Certificate Problem

On 12/18/2017 7:32 PM, Henrik37 wrote: > David E. Ross wrote: >> On 12/18/2017 1:17 PM, Henrik37 wrote: Oops - after a complete reboot, SM 2.49.1 does appear to have solved the problem. Does anyone have any idea or explanation about what has been going on? >>> Oops again - SM

Re: V2.48 Security Certificate Problem

David E. Ross wrote: On 12/18/2017 1:17 PM, Henrik37 wrote: Oops - after a complete reboot, SM 2.49.1 does appear to have solved the problem. Does anyone have any idea or explanation about what has been going on? Oops again - SM 2.49.1 DIDN'T fix my problem after all. More ideas sought.

Re: V2.48 Security Certificate Problem

David E. Ross wrote: On 12/18/2017 1:17 PM, Henrik37 wrote: Oops - after a complete reboot, SM 2.49.1 does appear to have solved the problem. Does anyone have any idea or explanation about what has been going on? Oops again - SM 2.49.1 DIDN'T fix my problem after all. More ideas sought.

Re: V2.48 Security Certificate Problem

Henrik37 wrote: Henrik37 wrote: Henrik37 wrote: Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when

Re: V2.48 Security Certificate Problem

On 12/18/2017 1:17 PM, Henrik37 wrote: >> Oops - after a complete reboot, SM 2.49.1 does appear to have solved the >> problem. >> >> Does anyone have any idea or explanation about what has been going on? > Oops again - SM 2.49.1 DIDN'T fix my problem after all. More ideas sought. Have you tried

Re: V2.48 Security Certificate Problem

Henrik37 wrote: Henrik37 wrote: Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to

Re: V2.48 Security Certificate Problem

Kapersky likely injects itself into SeaMonkey and intercepts https trafic but does not install its certificate. You probably have email and other browser connection options checking activated. There are a few older threads here and on mozillazine which have a similar tune. Personally I would

Re: V2.48 Security Certificate Problem

Henrik37 wrote: Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely,

Re: V2.48 Security Certificate Problem

Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely, websites will present

Re: V2.48 Security Certificate Problem

WaltS48 wrote: On 12/17/17 9:27 PM, Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to

Re: V2.48 Security Certificate Problem

WaltS48 wrote: On 12/17/17 9:27 PM, Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to

Re: V2.48 Security Certificate Problem

On 12/17/17 9:27 PM, Paul B. Gallagher wrote: Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely,

Re: V2.48 Security Certificate Problem

Henrik37 wrote: Here is a typical error message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely, websites will present trusted identification

Re: V2.48 Security Certificate Problem

Here is a typical errpr message: "This Connection is Untrusted You have asked SeaMonkey to connect securely to www.homedepot.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely, websites will present trusted identification to prove that you

Re: V2.48 Security Certificate Problem

On 12/17/2017 2:54 PM, Henrik37 wrote: > Since updating my Kaspersky Total Internet software to the 2017 version. > SM 2.48 is reporting lots of security certificate errors. > > Is this likely to be because SM 2.48 needs updating, a Kaspersky > problem, or something else? > > Thanks, in