On a Solaris 10 sparc machine, using pcsc and opensc both from
svn, there appears to be a mismatch of handing the length
field within the message for using a pin pad reader.
pcscd trace shows:
0126 ../../src/src/ifdhandler.c:1307:IFDHControl() ControlCode: 0x42330006,
usb:076b/3821:libusb:/d
Hello,
Martin Paljak wrote:
> What is the SET_PIN option supposed to do?
> Verify the first PIN and then set another PIN value to the second entry?
>
Yes.
For IAS/ECC and 'AuthentIC v3' cards
PIN unlocking is protected by another 'PIN' object.
> On Jul 27, 2010, at 3:41 PM, webmas...@opensc-
Hi,
What is the SET_PIN option supposed to do?
Verify the first PIN and then set another PIN value to the second entry?
On Jul 27, 2010, at 3:41 PM, [email protected] wrote:
>
> + case SC_PIN_CMD_SET:
> + ins = 0x2C;
> + p1 = 0x02;
> + if (data-
