Chrome showing SSL certificate errors for all Symantec certs

Same will happen to Firefox as well: https://blog.mozilla.org/security/2018/03/12/distrust-symantec-tls-certificates/

  • January 2018 (Firefox 58): Notices in the Browser Console warn about Symantec certificates issued before 2016-06-01, to encourage site owners to replace their TLS certificates.
  • May 2018 (Firefox 60): Websites will show an untrusted connection error if they use a TLS certificate issued before 2016-06-01 that chains up to a Symantec root certificate.
  • October 2018 (Firefox 63): Distrust of Symantec root certificates for website server TLS authentication.

Opera looks like they may follow Google shortly after: https://groups.google.com/a/chromium.org/forum/m/#!topic/blink-dev/eUAKwjihhBs
TarquinWJ Opera
Hi all,

A comment from Opera's perspective;

Like Chrome, Opera uses the rootstores provided by the platform, as well as Mozilla's NSS rootstore on platforms which do not provide their own. We therefore place a lot of trust in these rootstores, and the CAs that are included in them. We are very grateful to both Google and Mozilla for keeping as much of this discussion in public as possible, when deciding how best to deal with the current situation.

Where possible, we would like the resolutions to mitigate the specific incidents that have been identified - the intent is to solve a problem. Making arbitrary changes which do not prevent recurrences of the incidents serves little purpose, and should be avoided (they may also be included if they offer some positive benefit, but that should not affect the need for actual resolutions). Sanctions may have their place, but specific mitigations are best as long as there are good intentions from the parties involved.

Typically, we use the same approach as Chromium when deciding which certificates to blacklist, and we are likely to use whichever approach Chrome uses when dealing with the Symantec root certificates. Internally, our opinion is that Google's second proposal is the one that should be implemented, but failing that, we like Mozilla's fallback proposal outlined here:
https://docs.google.com/document/d/1RhDcwbMeqgE2Cb5e6xaPq-lUPmatQZwx3Sn2NPz9jF8/edit
 
Back
Top Bottom