Issue metadata
Sign in to add a comment
|
Certificate Transparency - GDCA CT Log Server Inclusion
Reported by
hanjie77...@gmail.com,
Mar 14 2016
|
||||||||||||||||||||
Issue descriptionWhat steps will reproduce the problem? Certificate Transparency - GDCA CT Log Server Inclusion Log Server URL: https://ct.gdca.com.cn HTTPS supported: yes MMD: 24 hours Contact Information: - email: capoc@gdca.com.cn; - phone number: +86(20)83487228-805 - Log Operator: Wang Shengnan Server public key: Attached file: gdca-ct-key-public.pem Accepted Roots: Attached file: gdca-trusted-roots.pem the "Merge Delay Monitor Root" already add in the trusted roots file. Log Description and Policy: Currently, the only policy in place is that the certificate chain to a publicly trusted root certificate. However, during the testing and log inclusion process, we are only including the GDCA trusted roots as authorized. Additional root entries will be evaluated after receiving an inclusion request. We will likely develop our policies further based on the results from the discussions in the Trans working group and our own internal policies. Such policies may include an enforcement of BR and EV standards, a requirement for at least organizational vetting on the certificate, minimum key sizes and hash algorithms, and similar checks. Chrome Version : 48.0.2564.116
,
Mar 28 2016
Can you tell me if there is any other steps need to be taken. Thank you!
,
Jul 8 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by msrchandra@chromium.org
, Mar 14 2016