Hello Ludovic, Thank you for replying!
Ludovic Rousseau wrote: > What do you call a provider? A PKCS#11 provider... >> The provider work with some other reader drivers... But not >> with CCID due to this issue. >> >> Is there any why to workaround this? > > I don't know yet any CCID reader supporting extended APDU. If you have > one such reader I can implement the support of extended APDU. >From what I know, the following support: 1. Athena ASEDrive IIIe USB V2 2. SCM SCR310, SCR335. 3. Gemplus GemPC Twin. Maybe I am wrong... But these readers work on Windows with the same PKCS#11 implementation... I was under the impression that it was quite common... I can help in test/debug what-ever needed in order to make it work!!! Is the vendor requirement for Extended APDU support is invalid? Is it missing from most of the readers? Best Regards, Alon Bar-Lev. _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
