You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating system and version: Win 11 Pro 10.0.22631 Build 22631
YubiKey model and version: Yubikey 5 - Firmware 5.4.3
Bug description summary:
When attempting to import an ECC 384 key using either the command-line or Yubikey Manager, it results in the error yubikit.core.smartcard.ApduError: APDU error: SW=0x6700
Edit: To summarize. It appears like a muppet, I had Yubikey Manager and ykman CLI in my Windows paths, and since Yubikey Manager GUI comes with an old version of ykman, they were fighting. So when I got the long error, it was from 5.0.4 on the Yubikey Manager's version. Then when I killed the windows path to Yubikey manager and kept only ykman, I had the correct version of 5.5.x.
So it wasn't really an issue, just a moment of confusion. I guess the only thing I really need is to understand what the error means:
ERROR: APDU length exceeds YubiKey capability
Which I googled, and could not seem to get an explanation on.
Edit 2:
I read through the source code for that error, which lead me to some defined value
And according to those docs, ECC384 should use an md of 384 bits But when I try that, same error. Also tried SHA256 for the digest, and yet again, same error.
Steps to reproduce
Generate ECC 384 via OpenSSL, then import into Yubikey Manager, or using the CLI with ykman piv certificates import
When attempting to import an ECC 384 key using either the command-line or Yubikey Manager, it results in the error
yubikit.core.smartcard.ApduError: APDU error: SW=0x6700
Edit: To summarize. It appears like a muppet, I had Yubikey Manager and ykman CLI in my Windows paths, and since Yubikey Manager GUI comes with an old version of ykman, they were fighting. So when I got the long error, it was from 5.0.4 on the Yubikey Manager's version. Then when I killed the windows path to Yubikey manager and kept only ykman, I had the correct version of 5.5.x.
So it wasn't really an issue, just a moment of confusion. I guess the only thing I really need is to understand what the error means:
Which I googled, and could not seem to get an explanation on.
Edit 2:
I read through the source code for that error, which lead me to some defined value
Then I found:
So I'm going to assume that this is referring to the message digest.
And according to those docs, ECC384 should use an md of 384 bits But when I try that, same error. Also tried SHA256 for the digest, and yet again, same error.
Steps to reproduce
Generate ECC 384 via OpenSSL, then import into Yubikey Manager, or using the CLI with
ykman piv certificates import
Expected result
Key should import
Actual results and logs
The following command runs fine:
However, when I run
I get the following error:
When I attempt to import using Yubikey Manager with elevated permissions, all I get is the red box with
SW=0x6700
Other info
Ensured I updated all drivers, CLI, and Yubikey Manager
The text was updated successfully, but these errors were encountered: