Skip to content
This repository has been archived by the owner on Feb 28, 2019. It is now read-only.

Bad CLA Response in U2F test not applicable to some NFC Authenticator #2

Open
qingzhang001 opened this issue Dec 20, 2016 · 0 comments

Comments

@qingzhang001
Copy link

qingzhang001 commented Dec 20, 2016

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?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant