GDCA root inclusion request for GDCA TrustAUTH R5 ROOT with Websites trust and EV

This case is GDCA’s request to include the "GDCA TrustAUTH R5 ROOT" certificate in Mozilla, enable the Websites trust bit, and enable EV treatment. The request began after GDCA reported that Firefox showed warnings for sites using certificates chaining to its root. Mozilla reviewed GDCA’s CP/CPS, audit statements, and BR self-assessment, and asked for multiple updates including domain-validation wording, audit URLs, and test-site information. GDCA provided revised CP/CPS documents, audit reports, and a BR self-assessment, and Mozilla later opened public discussion on the request. On 2017-07-27, Mozilla approved the request and said it would file the NSS and PSM bugs for the actual changes.

1. 2015-02-02 GDCA requested Mozilla add the GDCA TrustAUTH R5 ROOT certificate.
2. 2017-03-25 GDCA submitted a BR self-assessment comparing its CP/CPS with the Baseline Requirements.
3. 2017-07-27 Mozilla approved inclusion of GDCA TrustAUTH R5 ROOT with Websites trust and EV.

1. 2015-02-02 Global Digital Cybersecurity Authority Co., Ltd. (Formerly Guang Dong Certificate Authority (GDCA)) — GDCA opened the request and said Firefox warned that root certificates were not trusted for its test websites.
2. 2015-02-10 Mozilla representative — Mozilla accepted the bug and began information verification.
3. 2015-09-09 Mozilla representative — Mozilla said GDCA still needed to resolve revocation-check errors, provide audit URLs, and document domain-ownership verification procedures.
4. 2015-11-18 Global Digital Cybersecurity Authority Co., Ltd. (Formerly Guang Dong Certificate Authority (GDCA)) — GDCA said it updated CPS and EV CPS Section 3.2.5 with domain verification procedures.
5. 2016-08-03 Mozilla representative — Mozilla opened public discussion for the inclusion request.
6. 2017-03-25 Global Digital Cybersecurity Authority Co., Ltd. (Formerly Guang Dong Certificate Authority (GDCA)) — GDCA uploaded a comparison document on CP/CPS compliance with the Baseline Requirements.
7. 2017-07-20 Mozilla representative — Mozilla posted its assessment summary, including the root, trust bits, EV policy OID, audit references, and verification procedures.
8. 2017-07-27 Mozilla representative — Mozilla approved the request and said it would file the NSS and PSM bugs for the approved changes.