mirror_worker: sync Chrome cosigner registry - #296
Open
lukevalenta wants to merge 5 commits into
Open
lukevalenta wants to merge 5 commits into
lukevalenta wants to merge 5 commits into
Conversation
lukevalenta
commented
Sep 24, 2026
lukevalenta
commented
Oct 2, 2026
lukevalenta
marked this pull request as ready for review
October 2, 2026 18:24
lukevalenta
requested review from
a team,
bwesterb,
cjpatton,
lbaquerofierro and
mendess
as code owners
October 2, 2026 18:24
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.
Implements RTG-5259.
When
enable_chrome_cosignersis enabled, an hourly scheduled event fetches Chrome'scosigners.jsonand public-key bundle. A singleton Durable Object validates and atomically stores the normalized issuer registry, retaining the last-known-good snapshot when synchronization fails.Chrome issuers are expanded across their recognized issuance-log window and used by
add-checkpoint,add-entries,sign-subtree, and metadata. The existinglogsmap remains available for custom cosigners and takes precedence when an origin appears in both sources.Registry ingestion verifies exact HTTP responses, response-size limits, relative OIDs, log-number bounds, PEM fingerprint bindings, and pure ML-DSA-44 SPKIs. It also rejects changed content under an unchanged version and parseable timestamp regressions.