-
Notifications
You must be signed in to change notification settings - Fork 693
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
cosign complains "no maching signatures" #1170
Comments
Hi @yrro I can reproduce the error but only with cosign v2.0; It didn´t happen on the previous version of cosign. Just to confirm: you are using closing 2 locally, right? |
Yes, This also happens if I build from their (I am trying to get stackrox to verify the signature on our mirror of the images, it too is complaining that it can't verify the signature against the public key - but it doesn't give me any more information than that, hence me trying to figure out how to use |
Hi, @yrro. Cosign introduced breaking changes in release v2, so it can't verify artifacts that were signed using the previous v1. You are using Cosign correctly, but this image was signed using Cosign v1, thus the error you are getting. You can verify the image using Cosign v1. |
We can close the issue since the cosign version we're using for the upcoming release has been upgraded to v2. |
Thanks folks. I'm seeing this with
I guess it works! Though I think the |
I've not used cosign before so maybe I'm doing it wrong. I get:
Is this telling me that the image is signed but that I'm using the wrong public key?
The text was updated successfully, but these errors were encountered: