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 you try to connect securely, websites will present
trusted identification to prove that you are going to the right
place. However, this website's identity can't be verified.
What Should I Do?
If you usually connect to this website without problems, this error
could mean that someone is trying to impersonate the website, and
you shouldn't continue.
Technical Details
I Understand the Risks"
No problem here with 2.49.1.
I have loaded SM 2.49.1 and it didn't solve the problem.
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.
Here are the two types of error messages being received:
*****
Error message type 1:
This Connection is Untrusted
You have asked SeaMonkey to connect securely to patch.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 are going to the right place.
However, this website's identity can't be verified.
What Should I Do?
If you usually connect to this website without problems, this error
could mean that someone is trying to impersonate the website, and you
shouldn't continue.
Technical Details
patch.com uses an invalid security certificate.
The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.
Error code: <a id="errorCode"
title="SEC_ERROR_UNKNOWN_ISSUER">SEC_ERROR_UNKNOWN_ISSUER</a>
I Understand the Risks
If you understand what's going on, you can tell SeaMonkey to start
trusting this website's identification. Even if you trust the website,
this error could mean that someone is tampering with your connection.
Don't add an exception unless you know there's a good reason why this
website doesn't use trusted identification.
Error message type 2:
This Connection is Untrusted
You have asked SeaMonkey to connect securely to www.forbes.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 are going to the right place.
However, this website's identity can't be verified.
What Should I Do?
If you usually connect to this website without problems, this error
could mean that someone is trying to impersonate the website, and you
shouldn't continue.
This site uses HTTP Strict Transport Security (HSTS) to specify that
SeaMonkey only connect to it securely. As a result, it is not possible
to add an exception for this certificate.
Technical Details
www.forbes.com uses an invalid security certificate.
The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.
Error code: <a id="errorCode"
title="SEC_ERROR_UNKNOWN_ISSUER">SEC_ERROR_UNKNOWN_ISSUER</a>
*****
Does anybody have any idea where these messages are coming from?
Seamonkey V.2.49.1 or Kaspersky 2017 Internet Security?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
