-
Notifications
You must be signed in to change notification settings - Fork 789
Require new bundle format for signing and verification #4959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
aaronlew02
wants to merge
12
commits into
sigstore:main
Choose a base branch
from
aaronlew02:new-bundle-sc
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 5 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
28ccd1f
Verify blobs exclusively via sigstore-go
aaronlew02 d6d0a2f
Require new bundle format for sign-blob
aaronlew02 a2efab0
Verify blob attestations exclusively via sigstore-go
aaronlew02 2a70df6
Require new bundle format for attest-blob
aaronlew02 e3775b5
Verify attestations exclusively via sigstore-go
aaronlew02 baa6db0
Require new bundle format for attest
aaronlew02 4f33850
Verify images exclusively via sigstore-go
aaronlew02 4537ba6
Require new bundle format for sign
aaronlew02 de506c6
Update shared flags and helper logic
aaronlew02 d435b3b
Update core logic and delete legacy verification code
aaronlew02 5ac6312
Update e2e tests
aaronlew02 6c0cc72
Update docs
aaronlew02 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is throwing away the result of
ShouldUploadToTlog, so the attestation would be unconditionally uploaded to the transparency log.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whether the attestation would be uploaded to the transparency log depends on:
len(c.SigningConfig.RekorLogURLs()) > 0, which iftruewould enable the upload confirmation prompt.sigstore-go, which would upload because a log is present.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, so this is just about presenting the prompt? I see we do the same in sign/attest but override what's in the signing config, what's the reason for that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's to support users who want to sign a private container image without uploading to the transparency log.
If a user uses a signing config with a Rekor URL, but a private repository is detected:
shouldUploadreturns false, and execution proceeds without a Rekor upload. If the user agrees...shouldUploadreturns true and the signing config goes tosigstore-go, which would upload because a log is present.This matches current functionality.