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
For verifying the SCT cosign seems to assume that public keys are always going to be Elliptical. I also verified that if I spin up an instance of CT Log here: https://github.com/google/certificate-transparency-go/blob/master/trillian/docs/ManualDeployment.md#key-generation
With RSA keys, then cosign is unable to verify the SCT produced by the CT Log.
The assumption seems to be here: https://github.com/sigstore/cosign/blob/main/cmd/cosign/cli/fulcio/fulcioverifier/fulcioverifier.go#L57
And with some debugging magic enabled, it fails:
getting signer: getting key from Fulcio: verifying SCT: cannot verify RSA signature with *ecdsa.PublicKey key
So, I was planning to add other public key types supported for verification.
The text was updated successfully, but these errors were encountered:
I can't assign to myself, but I'll be happy to work on this.
Sorry, something went wrong.
+1!
Successfully merging a pull request may close this issue.
Description
For verifying the SCT cosign seems to assume that public keys are always going to be Elliptical. I also verified that if I spin up an instance of CT Log here:
https://github.com/google/certificate-transparency-go/blob/master/trillian/docs/ManualDeployment.md#key-generation
With RSA keys, then cosign is unable to verify the SCT produced by the CT Log.
The assumption seems to be here:
https://github.com/sigstore/cosign/blob/main/cmd/cosign/cli/fulcio/fulcioverifier/fulcioverifier.go#L57
And with some debugging magic enabled, it fails:
So, I was planning to add other public key types supported for verification.
The text was updated successfully, but these errors were encountered: