{"id":19688,"date":"2019-02-05T12:08:46","date_gmt":"2019-02-05T11:08:46","guid":{"rendered":"http:\/\/blog.netspark.de\/?p=19688"},"modified":"2023-07-05T09:35:25","modified_gmt":"2023-07-05T07:35:25","slug":"firefox-65-causing-problems","status":"publish","type":"post","link":"https:\/\/blog.netspark.de\/?p=19688","title":{"rendered":"Firefox 65 causing problems"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft  wp-image-8125\" src=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-480x480.png\" alt=\"\" width=\"64\" height=\"64\" srcset=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-480x480.png 480w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-150x150.png 150w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-768x768.png 768w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-1440x1440.png 1440w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-300x300.png 300w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-500x500.png 500w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew-64x64.png 64w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2018\/08\/FireFoxLogoNew.png 2000w\" sizes=\"auto, (max-width: 64px) 100vw, 64px\" \/>If you recently updated your firefox, you might have experienced<br \/>\nproblems with HTTPS sites. Main problem for the ominous<br \/>\nSEC_ERROR_UNKNOWN_USER problem are certificates from a<br \/>\nhandful of virus scanners. Among them are Kaspersky and Avast.<\/p>\n<p><!--more-->The problem however is well-known as it has to do with the way how virus scanners are scanning inbound and outbound HTTPS traffic. They act as a proxy and thus issue certificates of their own for the HTTPS connection. Firefox however cannot verify the origin of the local certificate against any of the global CAs thus presenting the error mentioned above.<\/p>\n<p>The most relaxing solution would be to import the local certificate of the virus scanner to Firefox&#8217;s certificate storage to have Firefox validate the usage of that certifcate once a secure HTTP connection is established.<\/p>\n<h2>This is Mozilla&#8217;s official workaround:<\/h2>\n<h3>Fixing the certificate errors in Firefox 65<\/h3>\n<p>If you have upgraded to Firefox 65 and are seeing errors when browsing the web that state the &#8220;Connection is not secure&#8221;, then you are most likely affected by this bug and seeing a conflict between the browser and your antivirus software.<\/p>\n<p>With this said, you have two options that can help you browser the web properly again, but neither option is ideal.<\/p>\n<p><strong>Option 1: Disable HTTPS scanning in your antivirus software<\/strong><\/p>\n<p>To temporarily fix this issue, you can disable HTTPS scanning in your antivirus program. This is not the recommended solution as you will no longer be protected from malicious SSL web sites.\u00a0<\/p>\n<p>The instructions on how to disable HTTPS scanning is different for each program. Below are various articles that explain how to disable HTTPS scanning:<\/p>\n<ul>\n<li><a href=\"https:\/\/support.avast.com\/en-ww\/article\/189\/\" target=\"_blank\" rel=\"nofollow noopener\">Avast<\/a><\/li>\n<li><a href=\"https:\/\/support.avg.com\/SupportArticleView?l=en&amp;urlname=Use-AVG-Antivirus-HTTPS-scan\" target=\"_blank\" rel=\"nofollow noopener\">AVG<\/a><\/li>\n<li><a href=\"https:\/\/support.kaspersky.com\/9927\" target=\"_blank\" rel=\"nofollow noopener\">Kaspersky<\/a><\/li>\n<li><a href=\"https:\/\/support.eset.com\/kb5833\/?locale=en_US&amp;viewlocale=en_US\" target=\"_blank\" rel=\"nofollow noopener\">ESET<\/a><\/li>\n<li>Bitdefender<\/li>\n<\/ul>\n<p>As Avast and AVG are on the process of pushing out a hotfix to disable HTTPS filtering in their products, you do not need to disable it in their program as that will cause this protection to be disabled for all browers on your computer.<\/p>\n<p>It should be noted that when you disable HTTPS scanning in your antivirus software&#8217;s web protection module, you are no longer protected malicious SSL sites. For this reason, we recommend the next option instead.<\/p>\n<p><strong>Option 2: Allows Firefox to use certificates from Windows certificate store<\/strong><\/p>\n<p>By default, Firefox 65 will use only use the certificates in their built in browser certificate store. It is possible, though, to enable the ability to also use the antivirus engine&#8217;s certificate that are created in the Windows certificate store to validate other\u00a0web sites certificates.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-19689\" src=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/avast-certificate.png\" alt=\"\" width=\"419\" height=\"521\" srcset=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/avast-certificate.png 419w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/avast-certificate-386x480.png 386w\" sizes=\"auto, (max-width: 419px) 100vw, 419px\" \/><\/p>\n<p>To enable Firefox to use the certificates installed as a Windows Trusted Certificate Authority, you can enable to the\u00a0security.enterprise_roots.enabled option. To do this, please follow these steps:<\/p>\n<ol>\n<li>Type\u00a0<strong>about:config<\/strong>\u00a0in the Firefox address bar and then press\u00a0<strong>enter<\/strong>. When Firefox asks, click on the button stating that you accept the risks.<\/li>\n<li>In the search field enter\u00a0<strong>security.enterprise_roots.enabled\u00a0<\/strong>and press enter.<\/li>\n<li>Double-click on\u00a0<strong>security.enterprise_roots.enabled <\/strong>so that it toggles to\u00a0<strong>true\u00a0<\/strong>as shown below.\n<div><a href=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/security_enterprise_roots_enabled-option.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-19691\" src=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/security_enterprise_roots_enabled-option-640x353.png\" alt=\"\" width=\"640\" height=\"353\" srcset=\"https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/security_enterprise_roots_enabled-option-640x353.png 640w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/security_enterprise_roots_enabled-option-768x424.png 768w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/security_enterprise_roots_enabled-option-500x276.png 500w, https:\/\/blog.netspark.de\/wp-content\/uploads\/2019\/02\/security_enterprise_roots_enabled-option.png 853w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/><\/a><\/div>\n<\/li>\n<li>You can now close the about:config page.<\/li>\n<\/ol>\n<p>You have now enabled Firefox to use the Avast root certificate\u00a0located in the Windows certificate store and you should be able to properly browse the web again.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you recently updated your firefox, you might have experienced problems with HTTPS sites. Main problem for the ominous SEC_ERROR_UNKNOWN_USER problem are certificates from a handful of virus scanners. Among them are Kaspersky and Avast.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[55,3,2949],"tags":[1778,3582,3267,2842,454,3581,3579,3580],"class_list":["post-19688","post","type-post","status-publish","format-standard","hentry","category-computer-2","category-news","category-technology","tag-authority","tag-avast","tag-ca","tag-certificate","tag-firefox","tag-kaspersky","tag-local","tag-virus-scanner"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/blog.netspark.de\/index.php?rest_route=\/wp\/v2\/posts\/19688","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.netspark.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.netspark.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.netspark.de\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.netspark.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=19688"}],"version-history":[{"count":0,"href":"https:\/\/blog.netspark.de\/index.php?rest_route=\/wp\/v2\/posts\/19688\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.netspark.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=19688"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.netspark.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=19688"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.netspark.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=19688"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}