Add registry revocations endpoint - #40
Merged
jvanulde merged 1 commit intoJul 3, 2026
Merged
Conversation
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
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.
What Problem This Solves
Issue #24 asks the registry to serve revocations per issuer. PR #39 created signed
revocations.jsonfiles and local CLI enforcement, but the registry had no way to publish or fetch those lists.Why This Change Was Made
This adds issuer-scoped revocation list storage to the registry and CLI helpers so revocation checks can use registry-hosted signed lists.
User Impact
qcap publish-revocations.qcap fetch-revocations.qcap opencan verify against a registry-hosted list using--revocations-url.Evidence
go test ./...inservices/qcap-registrycargo check --workspacecargo test -p qcap-clipowershell -ExecutionPolicy Bypass -File scripts/demo.ps1Fixes #24