Appendix
A
Using PC_to_RDR_Escape Command
The PC/SC layer does not allow the use of the SCardTransmit API unless the reader has previously signalled the presence and activation of a card. This prevents the use of commands such as the ICAO test commands or the HID commands without being able to properly recognize and activate a card. In order to be able to use these commands even without a previous card activation, the same functionality of pseudo-APDUs (CLA = 0xFF) is provided through the PC_to_RDR_Escape command.
To use the PC_to_RDR_Escape command with the default Microsoft CCID driver, the functionality must be first enabled in the Windows registry.
To issue the PC_to_RDR_Escape command without a card being present, the reader must be first opened with the SCardConnect function with the following settings:
dwShareMode = SCARD_SHARE_DIRECT
dwPreferredProtocols = 0
Then the vendor IOCTL for the Escape command is defined as follows:
#define IOCTL_CCID_ESCAPE SCARD_CTL_CODE(3500)
The following is an example of the call:
SCardControl(hCard, IOCTL_CCID_ESCAPE, …) or:
SCardControl(hCard, SCARD_CTL_CODE(3500), …)
The data in the lpInBuffer parameter of the length given in nInBufferSize are copied to the abData field of the PC_to_RDR_Escape command and all the data in the response in RDR_to_PC_Escape
abData field are copied back to the lpOutBuffer.
The abData field of the PC_to_RDR_Escape must contain the pseudo-APDU to be executed (typically, an ICAO test command or reader configuration). The maximum allowed size of abData in
PC_to_RDR_Escape
is currently 262 bytes and the maximum size of the response data in the abData field in the RDR_to_PC_Escape response is 464 bytes. The PC_to_RDR_Escape and RDR_to_PC_Escape do not support any form of chaining to extend the lengths of the supported parameters.
May 2017 93
94
Using PC_to_RDR_Escape Command PLT-03296, Rev A.0
This page intentionally left blank.
May 2017
PLT-03296, Rev A.0
This page intentionally left blank.
May 2017 95
hidglobal.com
