-
Couldn't load subscription status.
- Fork 644
Add support to download and attach for protobuf bundles #4477
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Zach Steindler <[email protected]>
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #4477 +/- ##
==========================================
- Coverage 40.10% 35.23% -4.88%
==========================================
Files 155 220 +65
Lines 10044 15230 +5186
==========================================
+ Hits 4028 5366 +1338
- Misses 5530 9176 +3646
- Partials 486 688 +202 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Support for attach signature would be somewhat strange, as it did not even support the old cosign bundle format (just raw signatures and certificates). If you do cosign sign and then cosign download signature, you should attach it with cosign attach attestation
I'm finding this pretty confusing, and I think users will have a hard time understanding it. Could we make it so that attach signature works for bundles?
Alternatively - I think the problem stems from the naming, where downloading/attaching bundles just isn't very well described by the words "attestation" or "signature" any more. What about adding a new subcommand attach bundle instead of trying to coerce attach signature and attach attestation to do this?
This was my first time using these commands and looking at how they were implemented, so I agree 😅. These commands are old (relative to the age of Cosign), implemented in 2021 and not really updated since 2023, so it's not surprising that Sigstore usage has evolved while these commands have not.
I think this is the most promising path forward. Looking over the flags again,
I agree generally, but I think we should wait a bit before tackling this problem. I want to make sure Cosign v3 is working for folks first, helping them transition to protobuf bundles, trusted roots, and signing configs, before we start changing the command set. But this is very much in scope for Cosign v4, and it's not just |
Signed-off-by: Zach Steindler <[email protected]>
Signed-off-by: Zach Steindler <[email protected]>
Summary
Continuing to make progress on #4470.
This adds protobuf bundle support for
cosign download attestationandcosign download signature(which will work if you docosign signwith the new protobuf format), as well as adding support forcosign attach attestationandcosign attach signature.This does not add any support (yet) for
cosign save.Release Note
download attestation,download signature,attach attestation, andattach signature(where you should use the new--bundleflag).Documentation
N/A