Ludovic Rousseau schrieb:
That's a way to see things :-)
Jean-Luc was not talking of readers in general but of CCID readers only.
He was also speaking about the GemPC433. Is this reader also ccid compliant? I thought not.
I'm asking this detail because I got a lot of different readers and smart cards but for some reason I still did not found a combination of USB reader, smart card, pcscd and open source driver that work together properly... :-(
What I have is:
Readers ------- Towitoko USB (and serial) CardMan USB (and serial) SCR335 USB (ccid) GemPC410 serial Cyberjack USB
Smart cards ----------- CardOS/M3 (T=1) CardOS/M4 (T=1) Starcos SPK 2.3 (T=1)
I also have some unidentified T=0 cards, but I can use them just for testing, not for the final application, which is written for only T=1 and should use only ITSEC level 4high evaluated products.
The CardMan USB readers work well with pcsc-lite, but only with the Omnikey proprietary beta driver and only one at a time, not in parallel. Since the driver is proprietary I cannot debug and find out where the problem really lies, if it is in pcscd or in the driver. Omnikey says their driver is capable of multithreading.
The Towitoko USB work with errors with the driver of Carlos Prados, so that I only get at most 2 working together.
The SCR335 with your ccid driver work only with the T=0 cards.
The GemPC410 works bad with CardOS and not at all with Starcos cards. I only tested it to know if it would be an option for me to buy the GemPC430 USB, since the two drivers have a big overlap. I decided *not* to buy the 430.
The Cyberjack USB is cutting the communication buffer with the card down to only 183 bytes, so it is not really an option to achieve efficiency.
After much testing it looks like I should buy a completely new set of readers, but this time I would like to be sure not to buy again the
wrong ones!
So please make a suggestion, if you had some money and would start from scratch, which kind of USB reader would you buy to be used together with pcsc-lite and your Gemcore and/or ccid drivers?
The requirement is that they should work in parallel, such that adding a reader increases the throughput of heavy load operations like digital signature.
Best regards Bettina Martelli
A CCID reader does not use a proprietary and confidential interface but a public interface [1]. That's why Jean-Luc and myself were able to write CCID drivers for a large part of (even unknown) readers and not just one reader from one particular manufacturer.
When I have the specifications of both a character-level reader and of an APDU level reader I prefer writing a driver using APDU.
To take Jean-Luc example: I prefer using ATDT to dial a number on a modem than sending each correct sound modulation on the line and deal with synchronisation, etc.
I think we are going off-topic :-)
Regards,
[1] http://www.usb.org/developers/devclass_docs/ccid_classspec_1_00a.pdf
-- Dr. Bettina Martelli, Development, TC TrustCenter AG Sonninstra�e 24-28, D-20097 Hamburg, Germany Tel: +49 (0)40 / 80 80 26-0 Fax: +49 (0)40 / 80 80 26-126
_______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
