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
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.
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.
The text was updated successfully, but these errors were encountered: