CA: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
=== Policy and Included CAs ===
== Policy and Included CAs ==


* [http://www.mozilla.org/projects/security/certs/policy/ Mozilla's CA Certificate Policy]
* [http://www.mozilla.org/projects/security/certs/policy/ Mozilla's CA Certificate Policy]
Line 14: Line 14:
* [[CA:MD5and1024|Dates for Phasing out MD5-based signatures and 1024-bit moduli]]
* [[CA:MD5and1024|Dates for Phasing out MD5-based signatures and 1024-bit moduli]]


=== CA Communications ===
== CA Communications ==


* [[CA:Communications | Communications sent to CAs]]
* [[CA:Communications | Communications sent to CAs]]


=== How to Apply for Root Inclusion or Changes ===
== How to Apply for Root Inclusion or Changes ==


* [https://wiki.mozilla.org/CA Process Overview]
* [https://wiki.mozilla.org/CA Process Overview]
Line 35: Line 35:
* [[CA:Certificate Download Specification|Certificate download specification]]. This document describes the data formats used by Mozilla products for installing certificates.
* [[CA:Certificate Download Specification|Certificate download specification]]. This document describes the data formats used by Mozilla products for installing certificates.


=== Discussion forums ===
== Discussion forums ==


The following Mozilla public forums are relevant to CA evaluation and related issues. Note that each forum can be accessed either as a mailing list or a  newsgroup (using an NNTP-newsreader or the Google Groups service).
The following Mozilla public forums are relevant to CA evaluation and related issues. Note that each forum can be accessed either as a mailing list or a  newsgroup (using an NNTP-newsreader or the Google Groups service).
Line 48: Line 48:
** mailing list: [https://lists.mozilla.org/listinfo/dev-security dev-security@mozilla.org]
** mailing list: [https://lists.mozilla.org/listinfo/dev-security dev-security@mozilla.org]


=== Work in Progress ===
== Work in Progress ==


* [http://www.mozilla.org/projects/security/certs/policy/WorkInProgress/ DRAFT of proposed next version of Mozilla's CA Certificate Policy]
* [http://www.mozilla.org/projects/security/certs/policy/WorkInProgress/ DRAFT of proposed next version of Mozilla's CA Certificate Policy]
Line 55: Line 55:
* [[CA:CAInclusionProcessIssues | Sandbox for identifying and resolving issues with the CA Inclusion Process]]
* [[CA:CAInclusionProcessIssues | Sandbox for identifying and resolving issues with the CA Inclusion Process]]


=== Templates ===
== Templates ==


The following are templates created by Gerv Markham for use by the Mozilla representative(s) responsible for working on CA requests. Except as noted the templates are used in creating comments for the bug report associated with a CA request.
The following are templates created by Gerv Markham for use by the Mozilla representative(s) responsible for working on CA requests. Except as noted the templates are used in creating comments for the bug report associated with a CA request.
Line 66: Line 66:
* [[CA:Inclusion_template|Inclusion in NSS]]
* [[CA:Inclusion_template|Inclusion in NSS]]


=== Obsolete ===
== Obsolete ==


The following items are obsolete, and have been replaced by other links provided above.
The following items are obsolete, and have been replaced by other links provided above.

Revision as of 19:55, 10 October 2012

Policy and Included CAs

CA Communications

How to Apply for Root Inclusion or Changes

  • Process Overview
  • How to Apply -- A guide for CAs wishing to include their certificate in Mozilla's Root CA store, and also a guide for CAs wishing to add trust bits or enable EV for a certificate that is already included in Mozilla's Root CA store.
  • Root Change Process. This wiki page describes how to change a root certificate that is currently included in NSS. This includes the process for disabling or removing a root certificate from NSS.
  • Checklist of CA information required to process a CA's application
  • Recommended practices for CAs wishing to have their root CA certificates included in Mozilla products
  • Potentially problematic CA practices. This discusses CA practices that are not explicitly forbidden by the Mozilla CA policy, and do not necessarily pose security issues, but that some people have expressed concerns about and that may cause delays in evaluating and approving CA applications. Some of these practices may be addressed in future versions of the Mozilla CA policy.
  • Queue for Public Discussion of CA evaluations
  • Technical recommendations for root certificates. This is a very first-cut attempt to outline what root certificates should contain, based on the relevant RFCs as supplemented by existing practices.
  • Checklist for Subordinate CAs and CSPs Information needed when subordinate CAs are operated by third parties.

Discussion forums

The following Mozilla public forums are relevant to CA evaluation and related issues. Note that each forum can be accessed either as a mailing list or a newsgroup (using an NNTP-newsreader or the Google Groups service).

  • Policy forum. This forum is used for discussions of Mozilla policies related to security in general and CAs in particular; among other things, it is the preferred forum for the public comment phase of CA evaluation.
  • Crypto forum. This forum is used for discussions of the NSS cryptographic library used in Firefox and other Mozilla-based products, as well as the PSM module that implements higher-level security protocols for Firefox, et.al. Note that this forum was previously used to discuss CA request, but such discussions should now be moved to the policy forum.
  • Security forum. This forum is used for discussions of Mozilla security issues in general. Crypto-related discussions should be moved to mozilla.dev.tech.crypto.

Work in Progress

Templates

The following are templates created by Gerv Markham for use by the Mozilla representative(s) responsible for working on CA requests. Except as noted the templates are used in creating comments for the bug report associated with a CA request.

Obsolete

The following items are obsolete, and have been replaced by other links provided above.