>> > as far as I know both are too much involved in opensc internals to port >> > them to pkcs#11 api. >> >> You have the correct understanding. > >ok, thanks.
I Will try to think about it. >> The question here is how the "feature" (pre-opened card handles) is >> implemented inside libopensc. The interface towards BaseCSP is indeed >> constant, but the implementation inside libopensc should be reviewed a >> bit, as there have been other (and alternative) implementations. Current >> reader-pcsc.c copypaste does not look like a long-term solution. >you know that code much better than I do. but didn't the cardmod reader >also share a lot of code with pcsc reader driver? IIRC that was the >argument for keeping it in that file, and not creating a new reader-cardmod.c >file. Yes, first patch included a new reader-opensccm, I give up this way. >what do you suggest should be done? and is it ok to commit the patch now >and work on it, or does it have to be changed before it gets into svn? >> How do I compile it, where do I download the SDK from? That should be <> documented in the wiki page for example. > >he posted some instructions last time. you need the cardmod.h file from >"Microsoft CNG Development Kit" (plattform SDK might contain it as well), >point configure to it, and you are done. to use it use the reg (older windows) >or inf (newer windows) files. These contain code for the Westcos cards >as far as I understand, and need to be extended to handle other cards >as well. Yes for now opensccm-westcos.reg it's a sample for extend to other cards (it can be generating I think by exe tool instand of being write once, like plug your card call : opensc-tool -carmod and use the card under windows). Opensccm.inf is to be extended with all card/atr managed by opensc (one file Will be enougth but require HID give by windows for each kind of card) >btw: François, do you know if several cards can claim one atr? >in that case we could claim all cards - the user can modify opensc.conf >to remove some drivers, thus opensc will not know the card and hopefully >ignore it / leave it to some other software. or can you have only opensc >or some other software installed, but never both? For exemple, actually, I use Outloock signing email, connect to linux serveur with puttysc and opensc-pkcs11.dll and access to secure website with Firefox (opensc-pkcs11.dll) all with my same card managed by opensc core. (this under windows 7). (When card is in use opensc Connect it with SCARD_SHARE_MODE and work with it) When cardmodule is in use each card managed by opensc (and present in .inf file) that you insert is take in account, reading certificats and put it in store ready to be use by application. >Regards, Andreas Regards, François
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
