2010/12/28 Martin Paljak <[email protected]>: > Hello, > On Dec 28, 2010, at 1:52 PM, Ludovic Rousseau wrote: >> 2010/12/28 Matteo Nastasi <[email protected]>: >>> If you explain me how I can compare USB messages on both the >>> systems to debug the problem I'm here. >>> >>> At opensc level the problem is that at: >>> 0x40a80950 07:25:21.940 [opensc-pkcs11] apdu.c:399:do_single_transmit: >>> unable to transmit APDU >>> the low level reply is only 1 byte instead 2. >> >> You are using OpenSC. You should ask for help on the opensc-user mailing >> list. >> http://www.opensc-project.org/opensc/wiki/MailingLists >> >> Maybe you are using a too old version of OpenSC. > > I asked Matteo to submit the logs as up to this point I was under the > impression that it was the CCID driver that was used, not the proprietary > reader with the proprietary driver. > > The problem is not with OpenSC, it works fine with other readers. A response > of "0x0A" is not a valid status response, so I suspect that the device is > bogus and that maybe the logs would help to identify the cause or be enough > evidence to mark the reader as unsupported. > > But it turns out to be the proprietary non-CCID reader. Which, of course, is > out of the scope of this list.
The driver is not proprietary. According to the Debian package the license of the driver is GNU GPL v2+. But the problem is clearly with the driver/reader. winscard_msg_srv.c:317:SHMProcessEventsContext() command TRANSMIT received by client 6 winscard.c:1647:SCardTransmit() Send Protocol: T=1 APDU: 00 2A 80 86 81 00 00 01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00 C8 47 D0 99 EE 44 42 A6 2D 0A 23 D8 EE D5 45 38 E5 3C F8 7D 2B 7E B0 AF A2 4E 1D 4A 6F E4 62 13 8A B3 DD 21 80 SW: 0A "0A" is not a valid value for a status word (SW). Matteo, you can try to report the bug to Ubuntu since you are using this system. You can also install Debian and try to reproduce the problem. If you have the same bug you can report it to Debian [2]. You may get more support from the Debian maintainer than from the Ubuntu "maintainers". Bye [1] http://packages.ubuntu.com/natty/libacr38u [2] http://packages.debian.org/sid/libacr38u -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
