Our browser extensions Avast Online Security and AVG Online Security are back on the Chrome Store, and on the Mozilla Store (since 12/17). We made changes to our extensions including limiting the use of data and these changes are explained clearly in our Privacy Policy. We are listening to our users and acknowledge that we need to be more transparent with our users about what data is necessary for our security products to work, and to give them a choice in whether they wish to share their data further and for what purpose. We have never compromised on the security or privacy of personal data. €œPrivacy is our top priority and the discussion about what is best practice in dealing with data is an ongoing one in the tech industry. Avast provided us with the following statement: Update: The extensions are available again. When you try to open one of the Store URLs of Avast or AVG extensions you get a "Oops! We can't find that page" error message. 2019: The https scanning related to Firefox in Avast or AVG could’ve been disabled by now, Avast’ Senior software developer Lukas Repacek confirmed in bug reported above that update has been pushed and user doesn’t need to do anything from their end.It appears that Mozilla removed these extensions from its Store. “Hi Ryan, Firefox HTTPS Filtering will be completely disabled by new virus engine update (eta 2hours from now) in Avast/avg products. UPDATE: Avast’s Security Researcher, David Jursa said, the company will push an update that will disable Firefox HTTPS filtering in Avast and AVG products. The company has already redesigned their certificate error page to show detailed information about which software has caused the issue and provides a link to SUMO page with certificate error codes for antivirus software and offers workarounds to fix those, but the change seems to have not shipped to version 65 and still available on Nightly. You either need to make the change in Firefox about:config or disable encrypted connections scanning in antivirus software to avoid this. Visit about:config (btw, we’ve new about:config page in Nightly, have a look)įind the preference security. Related: How to disable Avast’s HTTPS Scanning Feature Or if you’re using Kaspersky, reinstalling it known to fix the issue. Uncheck ‘Enable HTTPS Scanning’ and close Settings Window. Scroll down a bit and under ‘Configure Shield Settings, click ‘Web Shield’Ĥ. Click on menu > Settings > Protection > Core Shieldsģ. Click Customize for WebShield and uncheck ‘Enable HTTPS Scanning’, click ‘OK’.Ģ.Disable HTTPS Scanning in Avast (old versions) If you”re using Avast/AVG or other third-party antivirus software other than Windows Defender and affected, do the following.ġ. Note: Affected users reported it on Firefox help forums that the issue is noticed with Avast or AVG software installed.įix SEC_ERROR_UNKNOWN_ISSUER certificate issue in Firefox 65 If you’ve updated Firefox to version 65 released on Tuesday, Januand noticed you can’t access any websites, especially secure websites and receiving certificate error SEC_ERROR_UNKNOWN_ISSUER, check if you’ve Avast/AVG, Kaspersky or other security software installed, because the antivirus software tries to insert their own certificate for websites in Firefox and breaking sites by showing error.Īfter receiving numerous complaints on their support forum, Mozilla has stopped delivering Firefox 65 update to Windows users via automatic updates.Īfter updating to Firefox 65, Firefox users unable to access https websites and informed by the browser that their connection is not secure and provided an above-said error code to troubleshoot the issue.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |