-
Notifications
You must be signed in to change notification settings - Fork 42
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
NFCCTAP_GETRESPONSE doesn't supported #163
Comments
Hi, you are right. Our implementation currently uses P1=0x00 for NFCCTAP_MSG which indicates that the GET RESPONSE functionality is not supported. Could you share more details about what issues, if any, you're experiencing with the current implementation? |
Just for some situation that can not response real time such as authenticator long time processing or nfc reader short timeout. If support NFCCTAP_GETRESPONSE will be more robust. |
Thanks for suggesting this enhancement for robustness. I've looked into this and the |
Got it. |
The NFCCTAP_GETRESPONSE doesn't in android project, but supported in yubikit iOS project.
The standard in ctap2:
The NFCCTAP_MSG command send a CTAP message to the authenticator. This command SHALL return as soon as processing is done. If the operation was not completed, it MAY return a 0x9100 result to trigger NFCCTAP_GETRESPONSE functionality if the client indicated support by setting the relevant bit in P1.
p1:0x80
Thanks!
The text was updated successfully, but these errors were encountered: