Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
CA/Application Instructions: Difference between revisions
Jump to navigation
Jump to search
Make it a bit more clear that this is not for amateurs
m (added link to CA:RootTransferPolicy) |
(Make it a bit more clear that this is not for amateurs) |
||
| Line 11: | Line 11: | ||
'''IMPORTANT Items to Note:''' | '''IMPORTANT Items to Note:''' | ||
* Having a root certificate you control included in Mozilla's root store is not a trivial thing, but a significant responsibility. It means that, in the normal case, the world will trust you to correctly issue digital certificates identifying any website. There will be associated costs in maintaining the required security infrastructure and having it audited on a yearly basis. | |||
* The information listed in [[CA:Information_checklist|CA Information Checklist]] is expected to be publicly available so that it can be reviewed and referenced during the Public Discussion Phase and for future reference. | * The information listed in [[CA:Information_checklist|CA Information Checklist]] is expected to be publicly available so that it can be reviewed and referenced during the Public Discussion Phase and for future reference. | ||
* Having a root included in NSS is not a one-time effort. After a CA has a root included in NSS, it is expected that the CA will continue to be aware of ongoing discussions and updates to the Mozilla CA Certificate Policy. The CA is required to send regular updated audits to Mozilla. The CA is required to update their policies as the Mozilla CA Certificate Policy is updated. | * Having a root included in NSS is not a one-time effort. After a CA has a root included in NSS, it is expected that the CA will continue to be aware of ongoing discussions and updates to the Mozilla CA Certificate Policy. The CA is required to send regular updated audits to Mozilla. The CA is required to update their policies as the Mozilla CA Certificate Policy is updated. | ||