Auto-updated, it works, but just like 18.6.2347 (build 18.6.3973) and 18.6.2348 (build 18.6.3977) TLS1.3 in Mozilla Firefox 52.9 ESR doesn’t work when HTTPS Scan is enabled.
Does Avast rely on windows crypto.dll to scan the cryptography used?
I’m thinking about crypt32.dll, 'cause, for instance, Windows XP is not actually able to load TLS1.3 using crypto.dll, so all the browsers who rely on the default Windows engine can’t load them (Internet Explorer, Google Chrome, Chromium ecc).
Anyway, Microsoft will also release an update to support TLS1.3 later on the next year for companies who have the paid Extended Support and for Windows Embedded POSReady 2009 users.
Firefox, however, has its own cryptography manager and handles TLS1.3 just fine under XP already, but as long as Avast is not able to scan it and blocks its traffic, it’s pretty much useless.
I know that TLS1.3 is still yet to be deployed for many sites, but since version 18 is gonna be the latest version of Avast supported on XP, it would be nice to have TLS1.3 supported before the end of support.
Thank you in advance,
Frank.
OS: Windows XP Professional Service Pack 3 x86 - Microsoft Extended Support.
Is is also like that in the New 18.6.2349 (just released) version, not the beta and not the RC version but the NEW Version with the same bloody version number.
I really do hate this practice of keeping the same version number when going from beta or RC version to regular program update release.