Confirmed users, Administrators
5,526
edits
CA:RootTransferPolicy: Difference between revisions
Jump to navigation
Jump to search
m
→Physical Relocation
| Line 36: | Line 36: | ||
The new organization that received the root certificate's private key must follow [https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/ Mozilla’s CA Certificate Policy], and send Mozilla links to the [[CA:Information_checklist#Verification_Policies_and_Practices|public-facing CP/CPS documentation and annual audit statements]]. | The new organization that received the root certificate's private key must follow [https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/ Mozilla’s CA Certificate Policy], and send Mozilla links to the [[CA:Information_checklist#Verification_Policies_and_Practices|public-facing CP/CPS documentation and annual audit statements]]. | ||
The agreement between the original organization and new organization must take the Websites (SSL/TLS), Email (S/MIME), and Code Signing trust bit settings into account, and the original | The agreement between the original organization and new organization must take the Websites (SSL/TLS), Email (S/MIME), and Code Signing trust bit settings into account, and the original organization must inform Mozilla if one or more of the trust bits should be turned off. Of course, to turn on a trust bit the new organization will have to go through [[CA:How_to_apply#Enable_Additional_Trust_Bits_for_an_included_root|Mozilla's root change process]]. | ||
== Personnel Changes == | == Personnel Changes == | ||