-
Notifications
You must be signed in to change notification settings - Fork 547
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: cosign sign-blob
should accept --certificate
and --certificate-chain
#2635
Comments
Adds support for `--certificate` and `--certificate-chain` to the sign-blob command. Fixes sigstore#2635 Signed-off-by: Nathan Smith <nathan@nfsmith.ca>
What would those be used for? The purpose of including those flags for “cosign sign” is to attach them to the OCI image. For sign-blob, there is nothing to attach to. The use case I’m not sure if we support now would be uploading a certificate associated with a signing key to Rekor. |
Adds support for `--certificate` and `--certificate-chain` to the sign-blob command. Fixes sigstore#2635 Signed-off-by: Nathan Smith <nathan@nfsmith.ca>
Adds support for `--certificate` and `--certificate-chain` to the sign-blob command. Fixes sigstore#2635 Signed-off-by: Nathan Smith <nathan@nfsmith.ca>
They end up working together with |
SG, I would also test for how this interacts with Rekor. Though this is likely related to the other issue you filed regarding precedence between keys and certs. |
Yeah this was kind of a yak shave moment because I went to go test |
Adds support for `--certificate` and `--certificate-chain` to the sign-blob command. Fixes sigstore#2635 Signed-off-by: Nathan Smith <nathan@nfsmith.ca>
See also #2511 |
Description
While
cosign verify-blob
will accept a certificate and CA chain to verify against, it appears the signing command won't accept them. Feels reasonable to make these two commands symmetric.The text was updated successfully, but these errors were encountered: