Hello, On Jun 1, 2011, at 00:08 , Peter Koch wrote: > All our TCOS cards have a 6 digit PIN so we use a verify command with > fixed PIN length, i.e. 00 20 00 00 06. We hardcoded this into our > software and only use this dirty hack if our software has detected a > Dell USB Smartcarc Keyboard. > > Unfortunately OpenSC cannot do this as it does not know in advance what the > PIN length will be.
pin_cmd in TCOS driver in tandem with reader-pcsc.c can help to remedy the situation with another "bogus reader workaround" ? Actually I'm not sure if in case of unpadded PIN blocks, should the initial APDU prefix include CLA INS P1 P2 only or an additional 0x00 (which you refer to as empty Lc) or not ? IMHO CCID spec leaves room for interpretation there... I remember different behavior from different readers/cards and cards in different protocol mode. > I have no idea why your SCM reader behaves different under Windows and > Linux. Does it have old firmware? Probably. SPR532 with latest firmware should work quite OK on Linux, at least in T=0 mode. -- @MartinPaljak.net +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
