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
{{ message }}
This repository has been archived by the owner on Feb 28, 2019. It is now read-only.
For some NFC authenticator, on contactless protocol (NFC), it only supports one basic logical channel. So after select the FIDO applet, when apdu class is 0x01, this authenticator will ignore the channel number in class byte and direct the command to the applet, and Authenticator replies with success (9000).
As multi logical channel on NFC in authenticator is not a requirement in FIDO spec, can we remove this bad cla response test?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A copy of issue google/u2f-ref-code#143, content below:
In u2f_nfc_test.cc, in the below mentioned portion of code:
std::cout << "\nCheck Bad CLA Response";
CHECK_NE(0x9000, xchgAPDUShort(1 /* not U2F CLA, 0x00 */, U2F_INS_AUTHENTICATE, 0, 0, 0, "abc", &rapduLen, rapdu));
CHECK_EQ(0, rapduLen);
For some NFC authenticator, on contactless protocol (NFC), it only supports one basic logical channel. So after select the FIDO applet, when apdu class is 0x01, this authenticator will ignore the channel number in class byte and direct the command to the applet, and Authenticator replies with success (9000).
As multi logical channel on NFC in authenticator is not a requirement in FIDO spec, can we remove this bad cla response test?
The text was updated successfully, but these errors were encountered: