![]() Therefore and again, Eset SSL/TLS protocol scanning is not the source of this problem. Otherwise, you would see Eset's root certificate at the top of the certificate chain. Also I have excluded the web site from Eset SSL/TLS protocol scanning. The website certificate chain validation appears to be borked. to include a SHA-256 thumbprint.īut why does it work normally on pc without eset ?īelow is a screen shot of what is the problem in IE11. Sertigo needs to contact Microsoft in regards to updating their existing Win root CA store AAA Services root cert. You need to contact BCE and have them contact Sertigo, aka Comodo. Also and because SHA-1 encryption is now deprecated, only the SHA-256 thumbprint is being used for verification purposes by the OCSP servers. validation processing are using the same AAA Services root cert. Referring back to what I posted previously, it appears OSCP servers used in web site cert. ![]() Note that Microsoft browsers use the Win root CA store exclusively for web site cert. This is why the web site web site is fully accessible via FireFox and not so in Microsoft browsers. ![]() contains both SHA-1 and SHA-256 thumbprints whereas the Win root CA store cert. is not the same as that one present in the Win root CA store. It's listed under the name of "Comodo AAA Services root." It also matches that for the same cert. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |