Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Martin Paljak (martinmartinpaljak.net)
Date: Tue Dec 28 2010 - 06:51:58 CST
On Dec 28, 2010, at 1:52 PM, Ludovic Rousseau wrote:
> 2010/12/28 Matteo Nastasi <nastasialternativeoutput.it>:
>> 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.
> 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.
Another problem with ACS readers is that they re-use the same USB ID for *many* readers while I'm not sure the firmware of the readers or chip revision would be the same, at least I've seen differences.
Nevertheless, the issue is invalid in the context of the CCID driver...
Muscle mailing list