-
Notifications
You must be signed in to change notification settings - Fork 56
Support verifying Sigstore bundles #478
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
Merged
Merged
Changes from 7 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
638d632
_cli: Add support for verifying Sigstore bundles
tetsuo-cpp ce00d3c
treewide: Verify inclusion proof for Sigstore bundles
tetsuo-cpp 8e37dc7
_cli: Clean up comments
tetsuo-cpp 40a65c7
CHANGELOG: Add changelog entry
tetsuo-cpp fcd5a7d
_cli: Comment formatting
tetsuo-cpp a74fd8a
_cli: Rename to a private field
tetsuo-cpp a63c64d
CHANGELOG: Add PR link
tetsuo-cpp 8546c1f
Merge branch 'main' into alex/verify-bundle
woodruffw cbb1e53
Merge branch 'main' into alex/verify-bundle
woodruffw 03f7321
sigstore: remove "rekor bundle" support
woodruffw 1b32fc1
docs, sigstore: more pruning
woodruffw c397f8d
sigstore, test: devolve bundle handling, fix tests
woodruffw 24f291b
sigstore, test: lintage
woodruffw 6d7adc1
verify/models: docstring
woodruffw f13d6b6
test: fix offline test
woodruffw 36392d5
assets: remove old rekor bundle
woodruffw dc1cb3b
test: Add more test coverage for `InvalidMaterials` error cases
tetsuo-cpp 4d8cb62
sigstore, test: docs, API cleanup
woodruffw 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
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
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
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 isn't great, but we'll be able to remove it soon when we get rid of
--rekor-bundle
so I'm not too worried about it.The only problem I see is that even though this field is marked as internal, you still need to provide a value for it if you construct one yourself. But I don't think users of the API have a good reason to be doing that anyway.
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 also outputs a
RuntimeWarning
from Pydantic at runtime: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.
Yeah, I think we can do a little better than this API (both the private field and the manual initialization). I'll look into it.
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.
Hmm, maybe we can just remove
--rekor-bundle
outright? We never "actually" stabilized it (we've always emitted a warning said that it's temporary and will be removed in an upcoming release), and we never integrated it into other tooling (like the GH Action) or other expectations (e.g. CPython doesn't list it).Thoughts @di?
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.
Fine with me!
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.
Cool! I'll just yank all of that out, then, and save us from even having to think about this 🙂