-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add a bundle test for a dsse envelope containing an in-toto statement #159
Add a bundle test for a dsse envelope containing an in-toto statement #159
Conversation
Based on the example in https://blog.sigstore.dev/cosign-verify-bundles/ Signed-off-by: Samuel Giddins <[email protected]>
d296036
to
d12f919
Compare
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.
LGTM behaviorally, although I think we might want to rename the bundle here (if only because naming a file sha256:...
will make it harder to visually distinguish between file inputs and hash-literal inputs).
Any suggested names? I picked this since it's what |
Hmm, maybe |
I'll take this over and land it. |
Signed-off-by: William Woodruff <[email protected]>
Signed-off-by: William Woodruff <[email protected]>
8d96ace
Summary
There are no bundle tests where
"kindVersion":{"kind":"dsse","version":"0.0.1"}
and the dsse envelope payload is an in-toto statementBased on the example in https://blog.sigstore.dev/cosign-verify-bundles/
Release Note
Documentation