Am 02.02.2004 um 19:24 schrieb David Corcoran:
I didn't think it was supported on Microsoft's PC/SC in a uniform way. PC/SC Lite always recommended that the reader driver follow the
CTBCS / MCT way of doing a reader based pin entry through SCardControl. I think that is how the Kobil reader does it ....
Are you suggesting that for a device that's not capable of handling PIN input internally the reader driver should handle the PIN input?
If so, the problem I see with this approach is that the driver (ifdhandler) has no idea on how to ask for the PIN - should it use a UI or should it use stdio to ask for the information?
</jum>
On Feb 2, 2004, at 11:56 AM, Ludovic Rousseau wrote:
Le Monday 02 February 2004 � 09:45:53, Jens Miltner a �crit:<x-tad-bigger>*****************************************************************************
What I'm looking for is a way for an application to find out whether a
given reader supports intrinsic PIN input (i.e. has built-in keypad and
has a safe PIN input mode). Since PC/SC doesn't seem to account for
this, I figured one way would be to define a new tag to be passed to
IFDGetCapabilities (and hope that as many ifdhandlers as possible will
eventually implement support for this tag).
Does anyone here knows how this is done with Microsoft PC/SC?
It would be a bad idea to reinvent an incompatible solution to the same
problem.
Bye,
--
Dr. Ludovic Rousseau [EMAIL PROTECTED]
-- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle
David Corcoran <[EMAIL PROTECTED]>
Identity Alliance [http://www.identityalliance.com]
Smart Cards, Biometrics, Training, Identity Management
*****************************************************************************
</x-tad-bigger>
</jum>
