Confirm, administrator
5,526
edits
Changes
→Process Overview
# 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 :#* All of the certificates that are capable of being used to issue new certificates, and which directly or transitively chain to their root certificate(s) included in Mozilla’s CA Certificate Program that are not technically constrained as described in section 9 of [[CAhttps:CertificatePolicyV2//www.1#Technical_Constraints_or_Auditingmozilla.2FDisclosure_of_Intermediate_Certificates|nonorg/en-technicallyUS/about/governance/policies/security-constrained issuing certificates]] chaining up to root certificates in group/certs/policy/inclusion/ Mozilla's program, as well as data about their CA Certificate Inclusion Policy].#* Their [[CA:ImprovingRevocation#Preload_Revocations_of_Intermediate_CA_Certificates|revoked Revoked intermediate certificates]].
== Ways You Can Help ==
