Firefox 61/TLS 1.3 combined with Avast Antivirus

Avast Free Antivirus / Premium Security
1

The current release notes from Firefox 61 reported problems by using Firefox/TLS 1.3 combined with Avast Antivirus. Referring to this information, I would glad to know, which version of Avast is required which cause no connection problems by calling https websites. Perhaps the current version 18.5.2342 has already resolved this matter, but i don’t want to install the Firefox 61 before I have secure information about this.

Has anybody experiences by using the actual version of Firefox ??

Greetings,
svnupa

2

Avast fixed this with VPS 180628-8. No problems for me with current Avast and Firefox 61 on TLS 1.3 sites.

3

Thanks for your response. Are you sure a VPS Update change something of the functionality?? I cannot believe.

Where you have found the details for this change??

Has anybody else collected experiences by using firefox 61 and TLS 1.3?

Greetings,
svnupa

4

I have installed Firefox 61 und no problems by using TLS 1.3 websites. Obviously it is the right version of Avast.

Thanks for help.

Greetings,
svnupa

5

You are welcome.

VPS updates can modify actions and/or change some of the program components of Firefox without requiring a full release update.

6

If you’re still having issues with this I found a workaround on an official Firefox troubleshooting page which worked for me:
https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message#w_avast-and-avg-security-products

If you use a security product by Avast or AVG, it may be intercepting secure connections by default. Avast and AVG products may not be ready for the most recent and secure TLS 1.3 specification used in the latest versions of Firefox. As a result, Firefox users may see intermittent Secure Connection Failed error pages with the error code SSL_ERROR_RX_RECORD_TOO_LONG on secure websites such as Google and others. As a workaround, you can disable the interception of secure connections in your AVAST or AVG settings:

  1. Open the dashboard of your Avast or AVG application.
  2. Go to Menu > Settings > Components and click Customize next to Web Shield.
  3. Uncheck the box next to Enable HTTPS Scanning and confirm this by clicking OK.
7

@nks10

This workaround is not necessary. Obviously, from previous posts throughout the forum, Avast has corrected the problem. If you still have HTTPS Scanning disabled, you should enable it. If you still have this problem, update the Avast VPS.

8

Thanks Gopher John. I know the workaround and it is the reason why I have oppened this threat.
My opinion is the same: The HTTPS Scanner shouldn’t been disabled (especially all kinds of webpages should be scanned).

Thanks for all.
svnupa

9

Well, 180704-2 has reverted the fix. HTTPS scanning is making secure website unreachable unless HTTPS scanning is disabled.

10

https://forum.avast.com/index.php?topic=220234.msg1467938#msg1467938
In this case it was a streaming update that fixed things.