-
Notifications
You must be signed in to change notification settings - Fork 135
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
[feature] Support offline attestation verification: .sigstore file or persisted SET #716
Comments
Some updates from the official sigstore bundle PR: the bundle would be a JSON that has the following format, with a sigstore bundle intoto type:
The For multiple attestations, this bundle file would be concatenated as JSON lines. The current bundle format is much more simple, but is more prone to error:
where the body is actually the rekor representation, so not the actual DSSE payload. So this format would require distributing both the .intoto.jsonl and this. |
Filed #3750, will mark this as a dup. The bundle format should take precedence over individual files. |
This is a tracking issue and discussion for whether we should move to support the proposed Sigstore's attestation blob format when it is implemented
See https://docs.google.com/document/d/1gucjOA_bGyRjK6TeaOI-X5GIUv8WsPzeMDMkq25Kv4Y/edit#heading=h.we5fqok7jai5
sigstore/cosign#2131
Describe the solution you'd like
This would require outputting
.sigstore
files instead of.intoto.jsonl
attestation outputs for the blob builders and generators.These
.sigstore
files would contain information like signing cert or pk and rekor SET for offline verification.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: