Certificate Transparency - Addition of new trusted roots to Symantec CT Log ct.ws.symantec.com
Reported by
symantec...@gmail.com,
May 27 2016
|
||||||
Issue descriptionThis is notify that we will be adding new trusted roots to Symantec CT Log Server ct.ws.symantec.com Base64 Log ID: 3esdK3oNT6Ygi4GtgWhwfi6OnQHVXIiNPRHEzbbsvsw= Operator: Symantec Submitted for inclusion in Chrome: 2015-05-1 HTTPS supported: yes Maximum Merge Delay: 24 hours Contact: DL-ENG-Symantec-CT-Log@symantec.com Chrome inclusion status: Included. (since M45) Following new trusted roots will be added to Symantec CT Log Server C=CH, O=SwissSign AG, CN=SwissSign Gold CA – G2 C=CH, O=SwissSign AG, CN=SwissSign Gold Root CA – G3 C=CH, O=SwissSign AG, CN=SwissSign Silver CA - G2 C=CN, O=WoSign CA Limited, CN=Certification Authority of WoSign C=CN, O=WoSign CA Limited, CN=CA 沃通根证书 C=CN, O=WoSign CA Limited, CN=CA WoSign ECC Root C=CN, O=WoSign CA Limited, CN=Certification Authority of WoSign G2 <b>Chrome Version : <Copy from: 'about:version'></b> URLs (if applicable) : NA Other browsers tested: NA Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: NA Firefox: NA IE: NA What steps will reproduce the problem? NA What is the expected result? NA What happens instead? NA Please provide any additional information below. Attach a screenshot if possible.
,
May 27 2016
,
May 28 2016
,
Jun 2 2016
Thanks for the notification. In the future, could you update the original log inclusion ticket (https://code.google.com/p/chromium/issues/detail?id=483625) please, as it's easier to keep track of then. Could you also attach the actual certificates, rather than just their subject names please?
,
Jun 6 2016
Rob: Would you please propose a policy update, then? Symantec is following the stated policy to the letter - https://sites.google.com/a/chromium.org/dev/Home/chromium-security/certificate-transparency/log-policy
,
Jun 6 2016
,
Jul 25 2016
The policy has now been updated. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ranjitkan@chromium.org
, May 27 2016