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

SCardTransmit returns SCARD_PROTOCOL_ANY as the receive protocol #51

Closed
emaxx-google opened this issue Mar 15, 2017 · 0 comments
Closed
Assignees
Labels

Comments

@emaxx-google
Copy link
Collaborator

When the SCardTransmit function is called (either from JavaScript or from the NaCl client wrapper) without specified the desired receive protocol (this parameter is called pioRecvPci in the PC/SC-Lite C API), then our NaCl port returns with specifying the receive protocol as 3 (that is, SCARD_PROTOCOL_ANY) instead of the actual protocol (e.g. SCARD_PROTOCOL_T0).

This should be fixed. Note that the severity of the bug seems to be low as arguably this output argument is ignored by a typical middleware application.

/cc @LudovicRousseau Thanks to @LudovicRousseau for reporting this.

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

No branches or pull requests

1 participant