3 ms·
With Eset you get a message explaining the issue, similar to if your connection was blocked because malware was detected. I don't think this practice is a big
by Neil44 10y ago
With Eset you get a message explaining the issue, similar to if your connection was blocked because malware was detected.
I don't think this practice is a big issue because the local machine would have to be compromised for it to be an issue, in which case it's irrelevant because the game is over already. Also the alternative is not scanning ssl traffic for malware which has it's own very real risks.
- raesene6 10y agoThe issues I've mentioned (problems dealing with self-signed certs, Cert pinning and EV-SSL) don't have much to do with the client being compromised. They're examples of how SSL MITM (even assuming no implementation flaws) can damage user security by breaking the operation of SSL for user web access.