CA:FAQ: Difference between revisions

437 bytes added ,  25 August 2011
Line 91: Line 91:


The main phases involved in including a root certificate in Mozilla products are:
The main phases involved in including a root certificate in Mozilla products are:
# Creation and submission of the CA root certificate inclusion request
# The CA files a bug to request inclusion of their root certificate.
# Information verification
# A representative of Mozilla verifies the information provided by the CA.
# Public discussion
# A representative of Mozilla conducts a public discussion of the request in the mozilla.dev.security.policy discussion forum.
# Decision on inclusion
# A module owner or peer posts their recommendation for approval, denial, or further work in the bug.
# Code change for inclusion and associated testing
# If appropriate, the module owner or peer approves the request, then files a bug against NSS for the actual changes.
# A developer modifies the NSS code and the CA performs the testing.
# Future releases of Mozilla products include the new version of NSS.


=== What if I don't trust a particular CA? ===
=== What if I don't trust a particular CA? ===
Confirmed users, Administrators
5,526

edits