CA/Application Process: Difference between revisions

Jump to navigation Jump to search
added clarification that Mozilla's application process considers each root certificate
(→‎Who May Apply: Updated to align with version 2.6 of policy that removed requirement that roots benefit Mozilla users.)
(added clarification that Mozilla's application process considers each root certificate)
Line 15: Line 15:


The same process is used to request:
The same process is used to request:
* Root certificate inclusion for all CAs, even if the CA already has root certificates included in Mozilla's root store
* Enabling EV treatment for an already-included root certificate
* Turning on additional trust bits for an already-included root certificate
* Turning on additional trust bits for an already-included root certificate
* Enabling EV treatment for an already-included root certificate
* Including a new root certificate, even if the CA already has root certificates included in Mozilla's root store
* Including a renewed version of an already-included root certificate
* Including a renewed version of an already-included root certificate
** Consideration for inclusion is per root certificate (defined as the combination of Subject DN, Subject Public Key Information, and Subject Key Identifier). Approval of one root certificate does '''not''' imply that other root certificates owned by the same CA would be accepted.


The overall steps of the CA certificate inclusion and update process are as follows. There are [[CA/Bug_Triage#Root_Inclusion.2FChange_requests_and_EV_Treatment_Enablement_Requests|Bugzilla Bug Whiteboard tags]] corresponding to many of these steps.
The overall steps of the CA certificate inclusion and update process are as follows. There are [[CA/Bug_Triage#Root_Inclusion.2FChange_requests_and_EV_Treatment_Enablement_Requests|Bugzilla Bug Whiteboard tags]] corresponding to many of these steps.
Confirmed users, Administrators
5,526

edits

Navigation menu