Skip to content
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

Open
ken666lin opened this issue Dec 24, 2024 · 1 comment
Open

NFCCTAP_GETRESPONSE doesn't supported #163

ken666lin opened this issue Dec 24, 2024 · 1 comment

Comments

@ken666lin
Copy link

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!

@AdamVe
Copy link
Member

AdamVe commented Jan 8, 2025

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?

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

No branches or pull requests

2 participants