Emil Ghitta, QA [:emilghitta] Reporter
	Description • 5 years ago

[Affected versions]:
Firefox 63.0.3 
Firefox 65.0a1

[Affected platforms]:
Windows 10 64bit.

[Preconditions]:
Install BitDefender Pro 2019 (trial).

[Steps to reproduce]:
1. Launch Firefox 63.0.3 with a new, Non-ASCII profile. (ex: åÞÛÚ).
2. Close Firefox 63.0.3.
3. Launch latest nightly with the same Non-ASCII profile.
4. Access the https://twitter.com/ webpage.
5. Close latest nightly.
6. Launch Firefox 63.0.3 again
7. Access the https://twitter.com/ webpage.

[Expected result]:
The webpage loads successfully.

[Actual result]:
Steps 4 and 7: An error stating that the "connection is not secured" is displayed.

[Workaround]
1. Set the "security.enterprise_roots.enabled" pref to "true".

[Note]:
For further information regarding this issue, please view the following screencast: https://drive.google.com/file/d/1QwzgEYEiytnfeL7-61ntqFYxgY6_DNVV/view?usp=sharing

Please note that you may have to repeat step 3 and 4 a couple of times (2-3 times) in order to reproduce (sometimes this is reproducible from the first try).

It seems that BitDefender is not adding it's certificate inside the Certificate manager on Non-ASCII profiles.

	Emil Ghitta, QA [:emilghitta] Reporter
	Comment 1 • 5 years ago

Just an update note:
You don't have to launch a different version of Firefox (with the same Non-ASCII profile). Launching the same version (ex: 63.0.3) with the same profile several times (2-3 times) will also reproduce this issue.

	J.C. Jones [:jcj] (he/him)
	Comment 2 • 5 years ago

Other than just turning enterprise mode on for Windows by default, I don't know what to do here.

	Romain Testard [:RT]
	Comment 3 • 5 years ago

Emil, per Gijs suggestion, can you please confirm that there are certificates installed for other vendors (ESET, Avast or Kaspersky all default to installing their certs into our NSS store) into the profile (not just via the about:config pref to use the windows DB). If confirmed it means it is a BitDefender issue, not a Firefox issue and we can open a ticket with them.

	Emil Ghitta, QA [:emilghitta] Reporter
	Comment 4 • 5 years ago

Confirming here as well (for better transparency).

BitDefender:

- Tested using non-ascii profile (freshly created, using the default pref configurations). BitDefender fails to add it's certificate (verified by viewing the Certificate Manager) and leads to the issue that was mentioned in comment 0. 

Avast free antivirus 18.82356 (build 18.8.4084.0) and AVG Antivirus free 18.8.3071 (build 18.8.4084.0):

- Tested using newly created non-ascii profiles (using the default pref configurations). It seems that both Avast and AVG successfully adds the certificates inside the Certificate Manager.