We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description
When following the documentation for verifying signatures locally with certificates the mentioned command is:
$ cosign verify --certificate cosign.crt --certificate-chain chain.crt user/demo
However, when executing this locally you'll get:
Error: --certificate-identity or --certificate-identity-regexp is required for verification in keyless mode
Given that the validation option has been the same for quite a while, I'm assuming it's just a documentation issue; but wanted to check in here first before creating an issue in the docs repo.
Version
cosign: A tool for Container Signing, Verification and Storage in an OCI registry. GitVersion: 2.2.4 GitCommit: fb651b4ddd8176bd81756fca2d988dd8611f514d GitTreeState: "clean" BuildDate: 2024-04-10T21:57:27Z GoVersion: go1.22.2 Compiler: gc Platform: darwin/amd64
The text was updated successfully, but these errors were encountered:
Yes, that is a documentation issue, you'll see it correctly documented in https://docs.sigstore.dev/verifying/verify/#keyless-verification-using-openid-connect. Do you want to make the fix in https://github.com/sigstore/docs?
Sorry, something went wrong.
@haydentherapper yeah will go ahead and to that in a giffy, thanks for clarifying things!
Successfully merging a pull request may close this issue.
Description
When following the documentation for verifying signatures locally with certificates the mentioned command is:
However, when executing this locally you'll get:
Given that the validation option has been the same for quite a while, I'm assuming it's just a documentation issue; but wanted to check in here first before creating an issue in the docs repo.
Version
The text was updated successfully, but these errors were encountered: