Repository navigation
Allow HTTPS URL binding in signed Trust Manifests - #124
Open
jonathanhefner wants to merge 1 commit into
Open
jonathanhefner wants to merge 1 commit into
jonathanhefner wants to merge 1 commit into
Conversation
This was referenced Oct 6, 2026
jonathanhefner
force-pushed
the
agent/trust-manifest-url-binding
branch
from
October 8, 2026 17:38
ea6d822 to
be6803f
Compare
jonathanhefner
changed the base branch from
main
to
jonathanhefner/independent-trust-manifests
October 8, 2026 17:38
jonathanhefner
force-pushed
the
agent/trust-manifest-url-binding
branch
from
October 28, 2026 19:57
be6803f to
b982e99
Compare
jonathanhefner
changed the base branch from
jonathanhefner/independent-trust-manifests
to
main
October 28, 2026 19:57
Permit signed subjects to identify exact content or a live HTTPS resource. Keep digest presence and value symmetric with the entry, retain release-coordinate matching, and verify every present binding. Preserve digest-only mirror support and existing signed documents. Define URL-only binding before v1 so later consumers need not relax an already released mandatory-digest contract. Signed-off-by: Jonathan Hefner <jonathan@hefner.pro>
jonathanhefner
force-pushed
the
agent/trust-manifest-url-binding
branch
from
October 28, 2026 21:55
b982e99 to
8d01afe
Compare
jonathanhefner
marked this pull request as ready for review
October 29, 2026 22:01
This branch has not been deployed
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.
Summary
Allow a signed Trust Manifest to identify its artifact through a content digest, an HTTPS URL, or both.
Existing digest-bound manifests remain valid. When both bindings are present, both must verify.
Motivation
A contributor may want to endorse an artifact at a particular HTTPS location without pinning one fixed representation. Requiring a digest for every signed manifest prevents expressing that distinction.
Defining URL-only binding before v1 avoids later relaxing a digest requirement that v1 consumers would otherwise be entitled to enforce. Consumers requiring exact-content assurance can continue to require digest binding.
Rationale
URL binding is optional so digest-bound manifests can continue to support mirrors without endorsing a particular retrieval location. When selected, the signed URL must exactly match the entry’s URL.
When both a digest and URL are present, both must verify: a matching URL cannot excuse a failed content-integrity check.
See Allow URL Binding as an Alternative to Artifact Digests for details.