Am Mittwoch 03 Februar 2010 11:50:38 schrieb Martin Paljak: > Things to think about: > > - Will it be part of OpenSC (a cross-platform smart card library) or a > platform specific plugin? - If yes, do we package it with > opensc-x.x.x.tar.gz?
it would be fine with me to do that. > - If we include a windows minidriver in libopensc tarball, so should the > tokend be. Neither can be built or used on other platforms. also fine with me. the benefit would be: users of opensc API would be in the opensc source repository. we could let the world know, that everyone else should please use the pkcs#11 api instead of libopensc. if we keep card module and tokend seperate, we have to keep the api stable so they will work with the released new and old versions of opensc. as far as I know both are too much involved in opensc internals to port them to pkcs#11 api. > - I don't like the reader-pcsc.c contents at all. The same problem has been > addressed before, with different approaches, see > http://itacns.corp.it/hg/itacns/file/adc0b2ceec86/patches/300-env-scardhan > dle.patch for alternative example. well, but that is a restriction handed to us by microsoft windows base CSP right? we need to work with whatever microsoft build, even if we don't like their design. or is there a better way to work with that? > I applied the patch, what can I do with it on a Linux machine? nothing, you need microsoft CNG SDK or plattform SDK to compile the card module for windows. it is only for use with the microsoft base CSP. but then every cryptoAPI using application can access smart cards supported by opensc (at least in theory. in practice you needto setup registry and inf files first). Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
