Oubadah

The ESET root certificate is not pre-generated. Keeping SSL filtering enabled is strongly recommended and safer than having it disabled as the number of malware that utilizes encrypted communication is rising. With SSL scanning disabled, your system might be vulnerable to such malware. That doesn't address all of the issues raised in the article, and it's also irrelevant to Chrome users on Windows 7 because having the filter enabled makes the browser completely unusable. Do you have any comment on this Chrome problem? Why does it not seem to affect Windows 10?

This issue was never resolved on Windows 7, but it looks like it might be best to keep SSL/TLS protocol filtering disabled anyway: hxxp://users.encs.concordia.ca/~mmannan/publications/ssl-interception-ndss2016.pdf

I recently did a clean install of Windows 7 (after a brief foray into 10) and so I ended up upgrading to ESS9 at the same time. The first thing I noticed was that browsing in Chrome (x64) was brutally slow to load many pages. Totally unusable. Disabling SSL/TLS Protocol Filtering seems to have fixed it. Was it disabled by default in ESS8? Is there any risk in disabling it? Another thing that seems to be broken for me is Banking and Payment Protection. Nothing happens.