Hello Jozsef, cardmod is still experimental module but it should at end work with all cards supported by opensc,
for now I only test it on win7 with westcos card (that is my working configuration). So you need and you do it to add your ATR on configuration file yourself, Perhaps can you send me your ATR/ATRmask and the configuration file you set, I will have a look. An other point it's the support for T0 only protocol so if your card is T1 this doesn't work for now... When you said "it did not really worked" what do you mean? Hope I will help, François. François Leblanc Service Recherche et Innovation francois.lebl...@cev-sa.com Tél. : 02.33.77.65.00 Fax : 02.33.77.65.01 www.cev-sa.com Avant d'imprimer, pensez à l'environnement De : Jozsef Dojcsak <d...@t-online.hu> A: opensc-devel@lists.opensc-project.org Date: 28/04/2010 18:03 Objet : Re: [opensc-devel] Cardmod MiniDriver Problem Envoyé par : opensc-devel-boun...@lists.opensc-project.org First of all many thanks to Francois and Martin for their help! As I wrote, I managed to compile the cardmod mini driver with MSVC9 and later I also did cross-compile it on Linux. Then I tested the driver on both XP and Win7 with partial success, since I don't have a Westcos card.. And my last question in this topic: Is this mini driver intended for Westcos cards only, or it should work with any other PKCS15/OpenSC compatible cards? (Well, I customized the ATR for other cards, but it did not really worked) Cheers Jozsef Jozsef Dojcsak wrote: > Martin Paljak wrote: >> On Apr 27, 2010, at 13:18 , Jozsef Dojcsak wrote: >> >>> Hello, >>> the new OpenSC Minidriver feature is very interesting, so I compiled the >>> latest source code with MSVC9 and I also install the minidriver as >>> documented. It seems to function, but the certutil always gets stuck at >>> context creation: during detecting reader features SCardControl always >>> returns 00000001 and reader status check raises an error too: >>> 2010-04-27 11:32:36.811 =================================== >>> 2010-04-27 11:32:36.811 opensc version: 0.12.0-svn-r4267 >>> 2010-04-27 11:32:36.811 PC/SC options: enable_pinpad=1 >>> 2010-04-27 11:32:36.811 [cardmod] >>> reader-pcsc.c:1602:cardmod_detect_readers: called >>> 2010-04-27 11:32:36.826 Probing pcsc readers >>> 2010-04-27 11:32:36.826 gpriv->pcsc_ctx = CD010002, card_handle = EA010001 >>> 2010-04-27 11:32:36.826 lecteur name = OMNIKEY AG Smart Card Reader USB 0 >>> 4f:4d:4e:49:4b:45:59:20:41:47:20:53:6d:61:72:74:20:43:61:72:64:20:52:65:61:64:65 >>> :72:20:55:53:42:20:30:00 >>> 2010-04-27 11:32:36.826 Requesting reader features ... >>> 2010-04-27 11:32:36.826 SCardControl failed 00000001 >>> 2010-04-27 11:32:36.826 OMNIKEY AG Smart Card Reader USB 0 status check >>> 2010-04-27 11:32:36.826 event: 0x10122 >>> 2010-04-27 11:32:36.826 state: 0x0000 >>> 2010-04-27 11:32:36.826 card present >>> 2010-04-27 11:32:36.826 [cardmod] >>> reader-pcsc.c:1814:cardmod_detect_readers: returning with: 0 >>> 420.62.0: 0x80070057 (WIN32: 87): Microsoft Base Smart Card Crypto Provider >>> 420.69.0: 0x80070057 (WIN32: 87): \\.\OMNIKEY AG Smart Card Reader USB 0\ >>> >>> I tested with multiple readers and the same readers works perfectly with >>> the non-minidriver tests. Can it be a problem that I compiled with MSVC9 >>> instead on Mingw32? Or is my Windows XP (and not Vista or 7) test system >>> the reason for this error? >>> >> >> Does it work for you if it is compiled with mingw? I remember getting 000001 as well with SCardControl but IIRC that turned out to be a driver issue or something closely similar. Anyway, if SCardControl fails when detecting reader features, it should not affect the rest of communication. >> >> The cardmod reader driver is not the same as the pcsc driver in OpenSC so there can be differences and the other tests don't apply. >> > I will test the mingw compilation soon, and I am planning a simple > test with the cardmod reader driver, but my real problem is not the > SCardControl 000001 response, but the hanging of the certutil test > (sorry, I forgot to mention this). I just assumed that this hanging > state has something to do with the SCardControl failure. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
<<image/gif>>
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
