Draft: Mozilla Root Store Policy v3.1: Mass Revocation Planning Becomes a Trust Requirement#38
Draft
krakenhavoc wants to merge 1 commit into
Draft
Draft: Mozilla Root Store Policy v3.1: Mass Revocation Planning Becomes a Trust Requirement#38krakenhavoc wants to merge 1 commit into
krakenhavoc wants to merge 1 commit into
Conversation
Covers Ballot SC-089's Mass Revocation Planning requirement and its alignment into Mozilla's Root Store Policy v3.1, effective July 1 2026, with an operational angle on detecting revocation independent of expiry-based renewal monitoring.
Deploying web with
|
| Latest commit: |
d0bd423
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://97e51566.web-f5e.pages.dev |
| Branch Preview URL: | https://claude-confident-tesla-wgqvy.web-f5e.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Topic
Mozilla published Root Store Policy v3.1 on June 29, 2026, effective July 1, 2026. It folds CA/Browser Forum Ballot SC-089's Mass Revocation Planning requirement (new BR Section 5.7.1.2) into Mozilla's own trust criteria for CAs, alongside CP/CPS documentation requirements, mandatory Detailed Controls Reports, and a five-year cap on root key age at inclusion.
Why this topic, this week: the policy took effect July 1, 2026, squarely inside the last 7 days, falls directly under "Browser root program changes," and the underlying CA/Browser Forum ballot activity (SC-089) hadn't been covered on the blog yet.
Sources used
https://blog.mozilla.org/security/2026/06/29/improving-transparency-and-assurance-in-the-web-pki-mozilla-root-store-policy-v3-1/Uniqueness check
Checked against the most recent posts in
src/posts/, including:public-ca-eku-separation-june-2026.md(May 27) — covers Chrome Root Program Policy v1.8 and clientAuth EKU separation, a different root-program changesc098v2-caa-rfc8657-mandatory.md(May 20) — covers CA/Browser Forum Ballot SC-098v2 (CAA parameters), a different ballotlets-encrypt-generation-y-transition.md(May 13) — covers Let's Encrypt's Generation Y intermediate rollout, a different CA-specific eventNo overlap with MRSP v3.1 or Ballot SC-089 found in any existing post.
Notes
draft: false) so it renders in the Cloudflare Pages preview for this PR.npm run buildpasses with the new post included.