-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Signature verification failed, the private key doesn't match the certificate #203
Comments
How is configured your private key? Did you select PKCS#1 v1.5 padding? |
Is there a plan to support RSA-PSS key in |
My understanding is that Authenticode doesn't support RSA-PSS, but I may be wrong. |
Thank you for your answers @ebourg and for the great work you are doing. |
@oleksii-tymofieiev You're welcome. Do you think you could send your signing certificate with the RSA-PSS key to [email protected]? I'd like to do some tests and see if I can print a useful error message when such a key is used. |
Hi, |
@apique13 What command line did you use? |
Sorry, I think the problem is maybe the certificate on my yubikey. I tried with signtool too, there is no error, but the outpur file is not properly signed. |
Hi, I'm consistently getting
Signature verification failed, the private key doesn't match the certificate
I'm running JSign on Linux Ubunutu
I'm using GCP KMS and this is my command:
What I know:
openssl md5
on the certificate, and the public key and all match. I'm not sure how I can test the private key from GCP though.My only other idea is my certfile is incorrectly formatted. In some cases I can see people using .pem (chained certs) and documentation mentions PKCS#7 or P7B format.
My certfile looks like:
Is there anyway you can give more information on the certfile formatting? Is there further way to run the JSign program in debug or verbose mode? Perhaps that could help me spot an issue.
Thanks.
The text was updated successfully, but these errors were encountered: