-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
NFC APDU extended length not supported #214
Comments
I wasn't expecting extended length to be used for U2F since the requests are less than 256 bytes, but I suppose that doesn't mean extended length format won't be used. Thanks for reporting! @merlokk I think the issue is in
From wikipedia, the LC parameter can be up to 3 bytes.
I believe we just need to handle the case when LC is 3 bytes. |
If LE is an extended field: LC and LE must be in the same format. |
Yubikey neo, yubikey 5 NFC and feitian ePass supports it. |
What's great about using extended length: When sending the APDU command using it, the APDU response must also be extended length. For large FIDO certificates, this saves some roundtrips, as you don't need to use ADPDU chaining by sending mutliple GET RESPONSE commands. |
It needs to be supported. |
@dschuermann check #217 please |
@dschuermann Can you update to 2.4.0 and test again? |
Sry for the delay. I just got ahead and updated the solokey. It works now with extended APDU. Also the AID is now correct. Great work! |
According to https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-nfc-protocol-v1.2-ps-20170411.html#apdu-length it should be possible to use APDU extended length. This is not the case.
In the log of our FIDO client you can see that it uses a register command with extended length and gets error code 6700.
Without extended length it works:
The text was updated successfully, but these errors were encountered: