PROCERT request to add PSCProcert as a trust anchor

This case is PROCERT’s request to add the “PSCProcert” certificate as a Mozilla trust anchor. The request began after PROCERT reported that its certificate was not included in Firefox’s trust repository and asked Mozilla to recognize it. Mozilla then worked through the CA inclusion process, asking for policy documents, validation details, test websites, and audit statements, while PROCERT provided updated CPS documents and certificates. The thread also records technical follow-up on OCSP behavior, domain and email validation practices, and audit verification. In November 2012, Mozilla approved the request to include the PSCProcert certificate with all three trust bits, and an NSS bug was filed to add it as a trust anchor.

1. 2010-09-06 PROCERT requested that the PSC Procert certificate be added as a trust anchor.
2. 2011-03-16 PROCERT provided an updated CPS and said it had authorization to change the OCSP port.
3. 2012-10-08 Mozilla opened public discussion for adding the PSCProcert certificate and enabling all three trust bits.
4. 2012-11-08 Mozilla approved inclusion of the PSCProcert certificate and said it would file the NSS bug.
5. 2013-01-10 Mozilla asked PROCERT to respond to action items from a CA Communication.

1. 2010-09-06 Community commenter — PROCERT said the PSC Procert certificate was not included in Firefox’s trust repository and linked the issue to bug 489240.
2. 2010-09-06 Community commenter — Kevin Brosnan asked whether the reporter was a representative of AC ProCert and pointed to Mozilla’s CA application instructions.
3. 2011-03-10 Mozilla representative — Kathleen Wilson said the request could proceed, noted the OCSP port change would be addressed, and asked for clearer domain and email validation details.
4. 2011-03-16 Community commenter — PROCERT attached a new CPS and said it had received authorization from SUSCERTE to change the OCSP port from 8001 to 80.
5. 2011-04-05 Mozilla representative — Kathleen Wilson said the request was added to the queue for public discussion and asked PROCERT to complete remaining items before discussion.
6. 2012-10-10 Community commenter — PROCERT responded in public discussion about certificate policy OIDs and the OCSP responder’s missing ocspNoCheck extension.
7. 2012-11-01 Mozilla representative — Kathleen Wilson summarized the assessment and said she intended to approve inclusion of PSCProcert with all three trust bits.
8. 2012-11-08 Mozilla representative — Mozilla approved inclusion of the PSCProcert certificate and said it would file the NSS bug.
9. 2013-01-02 Community commenter — PROCERT asked for an update on the inclusion process and said it had not received email about the inclusion.
10. 2014-09-02 Mozilla representative — Kathleen Wilson said emails to @procert.net.ve addresses were bouncing and asked PROCERT to contact her or respond in the bug.