Am 09.02.2004 um 14:44 schrieb David Corcoran:
Hi,
No, the reader driver should not prompt for a PIN. The application (say
PKCS#11) should query the devices attributes. If the device supports
secure pin entry (Pin Pad on Reader) then the correct CT command is sent
through SCardControl to allow the reader to do secure pin entry. If the
reader does not have the attribute for secure pin entry the application
prompts for the pin and uses the usual SCardTransmit call to verify it
through the card ......
Aah, yes, but that was my original question: how do I determine the device attributes?
The GetCapabilities call (not sure what the application API would be called - I'm on the ifdhandler side) looked like a promising starting point, but I couldn't find a definition for a tag specifying I'm looking for this attribute...
</jum>
_______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
