CA/Root Store Policy Archive: Difference between revisions

From MozillaWiki
< CA
Jump to navigation Jump to search
(Add policy 2.4)
(Fix formatting)
Line 19: Line 19:
====2.4====
====2.4====


* [https://github.com/mozilla/pkipolicy/blob/2.4/rootstore/policy.md Policy document],  
* [https://github.com/mozilla/pkipolicy/blob/2.4/rootstore/policy.md Policy document], [https://github.com/mozilla/pkipolicy/blob/2.4/ccadb/policy.md Common CCADB Policy], [https://github.com/mozilla/pkipolicy/blob/2.4/ccadb/mozilla.md Mozilla CCADB Policy]
  [https://github.com/mozilla/pkipolicy/blob/2.4/ccadb/policy.md Common CCADB Policy],  
  [https://github.com/mozilla/pkipolicy/blob/2.4/ccadb/mozilla.md Mozilla CCADB Policy]
* Publication date: February 28, 2017
* Publication date: February 28, 2017
* Compliance date: February 28, 2017 (except "CP/CPS in English", which is June 1, 2017)
* Compliance date: February 28, 2017 (except "CP/CPS in English", which is June 1, 2017)

Revision as of 12:16, 28 February 2017

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.

Versions of the Policy

2.4

2.3

2.2

2.1

2.0

Earlier