On 05/12/06, Stef Hoeben <[EMAIL PROTECTED]> wrote:
Ludovic Rousseau wrote:
> Maybe you are talking of the secure PIN verify command using a PIN pad
> reader?
>
Yes, that what I mean -- sorry for the confusion.

So in the data for the SCardControl command, I could put
     00 22 00 02 04 FF FF FF FF
or so, but that would only work for 4 digit PINs (ASCII encoded)
nor for e.g. a 5 digit PIN.

I can't figure out how to set the values in the PIN Verification Data
struct  (bmPINBlockString, bmPINLengthFormat, etc.) so variable
length PIN blocks are supported.
(Yet it would be very stange if this shouldn't be supported in de
CCID pinpad specs...)

It is supported. But I have never tried it myself.
You should use something like:
1E0A820000100102010409000000000400000000200081 for the complete
SCardControl() data.

If I parse it correctly you have:
bmFormatString = 82
bmPINBlockString = 00
The APDU is just 00200081

Many readers are bogus or "limited" so it may not work with every reader.
The sample above is said to be working on a KOBIL Kaan Advanced with a
Telesec card.

Bye,

--
 Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to