- Mar 16, 2019
- 4,058
Kaspersky was experimenting with the same method used by Avast-AVG in their last beta but didn't push this change to the final version. Maybe they'll test again in the next beta.I have already decided to ditch Kaspersky and to revert back to Microsoft defender.
Only Avast-AVG can scan https and QUIC without inserting their certificate.
I asked ESET if they would consider the same method and Marcos from ESET forum told me,
I don't know how much truth is in that but I'm pretty sure that there must be some considerable downsides. Otherwise, everyone else would've opted for that method a long time ago.There has already been an internal discussion about this, and the cons substantially outweigh the benefits. We've also tested one of the mentioned AVs, and as we assumed, a malicious connection was not blocked, just reported while with ESET, it would have been blocked. This topic is still open, and if there is a way to perform SSL filtering differently without any negative effects on security, we will definitely consider it.
Last edited: