Google has made a conclusive decision on the different dates they want to execute as part of the accord plan in distrusting Symantec SSL Certificates.
Security engineers from Google and Firefox engineers discovered that Symantec misissued around 127 SSL certificates, as the investigation progress this underlying estimation developed to an outstanding figure of more than 30,000 certificates.
After the discovery, Google started removing support for Symantec SSL certificates gradually in Google Chrome. Mozilla also in the process of distrusting Symantec SSL certificates, hope they execute final plans soon. It affects Multiple brands owned by Symantec.
- Symantec
- GeoTrust
- Thawte
- RapidSSL
Symantec have been required to log all their certs to CT and so there is much better
transparency of issuance practice.
Also Read SSL/TLS Certificate Revocation is Broken Time for More Reliable Revocation Checking Mechanism
Partner Infrastructure December 1, 2017
Later Google announced SubCa proposal which was accepted by Symantec on 18th July.
The key aspect of this proposal is to exchange the authentication and issuance of certificates to a set of new SubCAs that are operated by “Managed CAs”, with the inevitable end state being a move from the current Symantec PKI to a modernized platform.
Symantec SubCAs capable of issuing SSL Certificates at this point and the certificates issued by new SubCAs infrastructure will continue to work with Chrome 70 (October 23, 2018).
It provides an option for webmasters to obtain certificates that continue to trust in Google Chrome version 70.
Chrome 66 April 17, 2018
Chrome 66 will start to show certificate errors with certificates issued by Symantec before June 1, 2016. It implies clients of Chrome 66+ won’t have the capacity to make a HTTPS connection with the site and they will get a notice.
Chrome 70 October 23, 2018
The Final stage will happen with the arrival of Chrome 70 (expected late October 2018). All Symantec certificates issued from their present roots will not be trusted on this date if legitimate re-issuance move was not made.
Webmasters and developers utilizing Symantec SSL certificates inside their application should connect with Symantec for another SSL certificate (issued through the SubCA accomplice), or contact another CA.
