CA/Root Store Policy Archive

From MozillaWiki
< CA
Revision as of 20:41, 30 November 2016 by Gerv (talk | contribs) (Remove list of things we are either never going to do, are in the BRs, have been superceded by events, or which have issued filed in Github)
Jump to navigation Jump to search

Process for Updating the Policy

The general process that will be followed to update the Mozilla CA Certificate Policy is as follows. Issues and potential changes will be tracked in the policy issue tracker.

  1. A Mozilla representative will bring forward an item for discussion in the mozilla.dev.security.policy forum.
  2. There will be a discussion of how, if at all, to modify the policy for the item.
  3. At some point, which may be at the start, a Mozilla representative will draft proposed text.
  4. A Mozilla representative will summarize a consensus that has been reached, and/or state the official position of Mozilla in both the discussion in mozilla.dev.security.policy and in the policy issue tracker.
  5. The draft policy in Github will be updated, if required.
  6. The issue will be closed.

At intervals, a new policy version will be released based on the current draft, along with a timeline for compliance.

Previous Versions of the Policy

2.2

2.1

2.0

Earlier

Items that belong in the Recommended Practices Wiki Page

List of items that may belong in the Recommended Practices wiki page:

Items that belong in the Potentially Problematic Practices Wiki Page

Items that may belong in the Potentially Problematic Practices wiki page.