|
|
| Line 89: |
Line 89: |
| === How does a CA certificate get included in Mozilla products? === | | === How does a CA certificate get included in Mozilla products? === |
|
| |
|
| For a high level description of the root inclusion process see: https://wiki.mozilla.org/CA
| | Mozilla's root inclusion process is described here: |
| | | https://wiki.mozilla.org/CA/Application_Process |
| For details about how a CA may apply for root inclusion see: https://wiki.mozilla.org/CA:How_to_apply
| |
| | |
| The main phases involved in including a root certificate in Mozilla products are:
| |
| # The CA files a bug to request inclusion of their root certificate.
| |
| # A representative of Mozilla verifies the information provided by the CA.
| |
| # A representative of Mozilla conducts a public discussion of the request in the mozilla.dev.security.policy discussion forum.
| |
| # A Mozilla CA Certificates Module owner or peer posts their recommendation for approval, denial, or further work in the bug.
| |
| # 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 to include the root certificate, and the CA tests the change.
| |
| # 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? === |