CA/Symantec Issues: Difference between revisions

CA/Symantec Issues (view source)

891 bytes added , 11 October 2017

Add dates for Symantec

Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti

4,925

edits

@@ Line 1: / Line 1: @@
+Following the investigation documented below, a [https://groups.google.com/a/chromium.org/d/msg/blink-dev/eUAKwjihhBs/El1mH8S6AwAJ consensus proposal] was reached among multiple browser makers for a graduated distrust of Symantec roots. The dates in that proposal and how they apply to Mozilla's Root Program and Firefox are as follows:
+* December 1st, 2017: Symantec to implement "Managed CA" proposal
+* April 17th, 2018: Dis-trust of all Symantec certificates issued before 2016-06-01 (in practice, to be implemented in Firefox 60 on May 1st)
+* October 23rd, 2018: Final dis-trust of Symantec roots (in practice, to be implemented either in Firefox 63 on October 16th or Firefox 64 on November 27th)
+It is planned for Firefox 58 (January 16th, 2018) to also feature a console warning for Symantec certificates issued before 2016-06-01 to help sites notice they need to migrate.
+-----
 This page lists all confirmed issues involving the CA "Symantec". It may be further updated by Mozilla as more information becomes available. Please do not edit this page yourself; if you have proposed changes, email [mailto:gerv@mozilla.org Gerv]. Information here is correct to the best of Mozilla's knowledge and belief. Symantec has also [https://bug1334377.bmoattachments.org/attachment.cgi?id=8867735 confirmed] the accuracy of the information, although errors transcribing their statements into this page remain Mozilla's.