-
-
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
Error with a Yubikey FIPS in PIV mode: The parameters in the data field are incorrect #225
Comments
Thank you for reporting this issue. What is the version of the Yubikey firmware? Does it work better if you install the Yubico PIV Tool and use |
Hi! I very much appreciate your assistance friend. Looks like 5.4.2 (also see below). I tried
|
There is something weird with the slot 9A, the algorithm of the private key (ECCP256) doesn't match the algorithm of the public key (ECCP384). How did you load the private key and the certificate on the Yubikey? Did you generate the private key on the Yubikey yourself and Sectigo sent the certificate, or did Sectigo send the preloaded Yubikey directly? |
Hi! Indeed, I noticed that but didn't consider myself expert enough to identify that as an issue. Silly me -- to assume that the Yubikey would verify that an imported crt matches the private key before accepting it! I've contacted Sertigo and getting a reissue on ECCP384. Hopefully this explains my issues in which case I will be proud to tells others about jsign. Will report back here later today. Emmanuel! Your work is most appreciated! |
Ok, it's confirmed that Sectigo sent me the wrong cert (sending a ECCP384 rather than ECCP256). I am rather unimpressed that Yubikey merrily imports a cert without doing any verification. Anyway, jsign is signed no problem with a newly issued ECCP384 and imported cert. My only thought was that if jsign caught this exception in a meaningful way and describe what was happening that may help. If there was a bad cert in there but happened to be ECCP384, you wouldn't have been tipped off. Thank you again Emmanuel! My favorite name! <3 |
Yes I agree. Jsign performs a basic verification after the signature is created, and a mismatch between the private key and the public key is reported: But the issue here appears before the signature is created, the Yubikey refused to sign the payload. I have to investigate why. |
Hi gents, appreciate all the work that's gone into jsign!
I am getting an exception that is not clear when signing from a Yubikey FIPS 5. I have verified things are working somewhat by changing
storepass
and it is returning an appropriate bad pin error.Flipping through things I suspect the issue is the jsign side. Using jsign 6.0.0 on Windows 11 (through Cygwin).
The text was updated successfully, but these errors were encountered: