Open Bug 1674946 Opened 4 years ago Updated 3 years ago

After the the installation of Seamonkey, Webpages browsing is not possible : connexion not certified on all webpages.

Categories

(SeaMonkey :: Security, enhancement)

enhancement

Tracking

(Not tracked)

REOPENED

People

(Reporter: spyhunter6155, Unassigned)

Details

Attachments

(1 file)

867.29 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0

Steps to reproduce:

Windows 10 64 Pro bIts
Seamonkey 2.53.4
Kaspersky Internet security 2020

I have done a clean install of Seamonkey (no previous folder or registry keys on the system)

Actual results:

After the install and when the Browser opened to the start page (www.seamonkey-project.org) in replacement to the normal page , you got a message saying that the connection is not certified (...)
Same for every other website , like google.com , yahoo.com , youtube ...
This is happening with Kaspersky installed on the system but it could be possible that other security solution leads to the same result.

Expected results:

The browser should open all Https websites normally.
Main workaround : specify to the browser's configuration the use of this below in the "about:config" section :

"security.enterprise_roots.enabled => true"

It could be configure by default on Seamonkey's installer.

You probably have enabled scanning of encrypted traffic in Kapersky. It is acting as a man in the middle. Root cause for these problems are missing certificates from the AV vendor. Personally I would disable this "feature" but if you do not want to do this see:

https://support.kaspersky.com/14620

We will not set security.enterprise_roots.enabled to true by default right now.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID

Well, i know all of this.

And, the link you provided on your comment is the exact same link i provided myself on the .doc file attached ("https pages after installation.docx").

What i trying to explain here, is : why SeaMonkey is the only browser still facing that type of issue where, all others browsers including Firefox long time solved this issue ?

Why disable a feature on Kaspersky or any other security suite, when is working properly on others browsers ?

It's not giving a good image of the web browser where a new user wants to test SeaMonkey and, the only thing he got, are errors.

Let it unable to browse any websites.

What is the purpose of any web browser.

As a general information, Kaspersky is not the problem here because, as described on the link below , other security suite could create this type of issue : https://support.mozilla.org/en-US/kb/error-codes-secure-websites (table of contents > antivirus products).

What i also explained earlier.

I think that this should be reconsidered because of the nature of the issue it represent and the way it penalize SeaMonkey.

Why disable a feature on Kaspersky or any other security suite, when is working properly on others browsers ?
It's not giving a good image of the web browser where a new user wants to test SeaMonkey and, the only thing he got, are errors.

I just look at it differently. For you it is a feature. For me it is a security risk. Making scanning your encrypted traffic easier is not something I generally want. There were already a few bugs where malicious code could have taken over the AV programm. It called enterprise for a reason. They usually use own certificates for intranet sites. Just a difference of opinion. I will bring it up again at the next meeting so you donÄt think I want to shovel it just under the rug.

Status: RESOLVED → REOPENED
Type: defect → enhancement
Ever confirmed: true
Resolution: INVALID → ---
Version: SeaMonkey 2.53 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: