Thawte certificates are supposed to be invalid since Chrome 70, but I have Chrome 70.0.3538.102 and it accepts certificate of this site just fine. Does anyone know, why that is? Should I be worried?
asked Nov 15, 2018 at 19:35
-
It does not accept this site for me: NET::ERR_CERT_SYMANTEC_LEGACY, Chrome 70 on Linux. Have you looked at the certificate chain? Maybe you have some local antivirus doing SSL interception which results in Chrome getting a certificate signed by a different CA?– Steffen UllrichCommented Nov 15, 2018 at 19:39
-
@SteffenUllrich Does not accept for my roommate either, but it does for me. Maybe its Win 8.1? It is weird. And yes, I have ESET but I see thawte in Chrome, that is how I spotted it.– Peter HarmannCommented Nov 15, 2018 at 19:41
-
Maybe you have manually added the CA to your Windows Truststore. This could also be done by some software installer. It is a good idea to clean out that list regularly. Unlike Firefox Chrome does not have its own store (I am however not sure how they revoke certs, if this applies also to modified CA stores)– eckesCommented Nov 16, 2018 at 2:52
-
@eckes removing the CA manually prevents me from accessing the page, but it is different. That is standard invalid cert. It should show symantec legacy error.– Peter HarmannCommented Nov 16, 2018 at 9:45
Add a comment
|
1 Answer
Weird phased rollout mechanism.
Their rollout mechanism was supposed to be "in v70 it STOPS working!". But now they seem to have settled on something like "in v70 it will show a warning in the dev console and stop working for SOME (tm) users! And we will phase it in completely when we feel like it."
Details here:
answered Nov 16, 2018 at 11:45
-
I suspected it may be the slow rollout Google does sometimes, but the blog said it will be distrusted by 70 immediately and that made more sense to me for a security update. Thanks for the information. Commented Nov 16, 2018 at 12:16