CA/Application Process: Difference between revisions

Jump to navigation Jump to search
Line 3: Line 3:
== Process Overview ==
== Process Overview ==


[bullet points - one sentence each, active verbs]
It can take up to two years for a CA to make it from one end of the process to the other. The overall steps of the process are as follows.


* ... Information Gathering
# [[CA:How_to_apply#Creation_and_submission_of_the_root_CA_certificate_inclusion_request | Submit a request for root inclusion.]]
* ... Verification
#* Note: This is done by an official representative of the CA. If you would like to see a particular root certificate included in Mozilla products, then please contact the CA who operates that root certificate.
* ... Added to Queue
# [[CA:Information_checklist | Provide information about the CA, and operation of the root certificate(s). |
* ... Public Discussion
# [[CA:How_to_apply#Information_Verification | Verify the information provided by the CA.]]
* ... Updated processes
# [[CA:Schedule | Add the request to the queue for public discussion.]]
* ... NSS patch
# [[CA:How_to_apply#Public_discussion | Participate in discussions of CA requests further up in the queue.]]
* ... NSS release
# [[CA:How_to_apply#Public_discussion | Respond to questions and concerns posted during the public discussion of the CA's request.]]
* ... Product releases
# [[CA:How_to_apply#Public_discussion | Complete action items resulting from the public discussion,]] which may include updating processes, documentation, and audits; depending on the action items, a second round of public discussion may be needed.
 
# [[CA:How_to_apply#Inclusion | Create a bug requesting the actual changes in NSS (and PSM for EV treatment).]]
It can take up to two years for a CA to make it from one end of the process to the other.
#* A representative of the CA must confirm that all the data in this bug is correct.
#* A Mozilla representative creates a patch with the updated trust bit, and provides a special test version of Firefox.
#* A representative of the CA uses the test version of Firefox to confirm (by adding a comment in this bug) that the certificate trust bits have been correctly updated.
#* The Mozilla representative requests that another Mozilla representative review the patch.
#* The Mozilla representative adds (commits) the patch to NSS, then closes this bug as RESOLVED FIXED.
#* At some time after that, various Mozilla products will move to using a version of NSS which contains the certificate. This process is mostly under the control of the release drivers for those products.


== Ways You Can Help ==
== Ways You Can Help ==
Confirmed users, Administrators
5,526

edits

Navigation menu