itman 1,752 Posted April 15, 2019 Share Posted April 15, 2019 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,281 Posted April 16, 2019 Administrators Share Posted April 16, 2019 If you didn't add the ESET root CA certificate there yourself, it could be that Windows added it. Unfortunately, we have no clue why it would have done so, however, it won't do any bad if it's there. Link to comment Share on other sites More sharing options...
itman 1,752 Posted April 16, 2019 Author Share Posted April 16, 2019 5 hours ago, Marcos said: Unfortunately, we have no clue why it would have done so, however, it won't do any bad if it's there. No, I certainly didn't add it. Also, not so sure on the "won't do any bad if it's there." Part of the browser SSL protocol handshake is for the web site server to download its Root CA certificate issuing cert. to the browser's Intermediate CA store for validation purposes. Also and obviously, IE11 will initially populated its Intermediate CA store with what exists in the Win Intermediate CA store at browser startup time. As I see it, Eset's root CA store certificate should only reside in the Win root CA certificate store since it is only used for internal decryption purposes. Link to comment Share on other sites More sharing options...
Recommended Posts