Confirmed users, Administrators
5,526
edits
CA/Application Process: Difference between revisions
→Process Overview
| Line 28: | Line 28: | ||
#* A representative of Mozilla adds (commits) the patch to NSS, then closes the NSS bug as RESOLVED FIXED. | #* A representative of Mozilla adds (commits) the patch to NSS, then closes the NSS bug as RESOLVED FIXED. | ||
# Mozilla products move to using a version of NSS which contains the certificate changes. This process is mostly under the control of the release drivers for those products. See [https://wiki.mozilla.org/RapidRelease/Calendar Mozilla's Release Calendar.] | # Mozilla products move to using a version of NSS which contains the certificate changes. This process is mostly under the control of the release drivers for those products. See [https://wiki.mozilla.org/RapidRelease/Calendar Mozilla's Release Calendar.] | ||
# After inclusion of the CA's root certificate, a representative of Mozilla issues a [[CA:SalesforceCommunity|CA Community Salesforce]] license to the [[CA:Information_checklist#CA_Primary_Point_of_Contact_.28POC.29|Primary Point of Contact]] for the CA. | |||
# The CA [[CA:SalesforceCommunity#Data_that_CAs_can_Add.2FModify|enters data into the CA Community in Salesforce]] for all of the [[CA:CertificatePolicyV2.1#Technical_Constraints_or_Auditing.2FDisclosure_of_Intermediate_Certificates|non-technically-constrained issuing certificates]] chaining up to root certificates in Mozilla's program, as well as data about their [[CA:ImprovingRevocation#Preload_Revocations_of_Intermediate_CA_Certificates|revoked intermediate certificates]]. | |||
== Ways You Can Help == | == Ways You Can Help == | ||