>-----Message d'origine----- >De : Andreas Jellinghaus [mailto:a...@dungeon.inka.de] >Envoyé : mercredi 3 février 2010 12:26 >À : Martin Paljak >Cc : François Leblanc; opensc-devel@lists.opensc-project.org >Objet : Re: [opensc-devel] Add card minidriver base on trunk.
(...) >> - 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? > Exactly for now I don't have better way to make link betwin windows and opensc And this is more secure than the patch since forbidden function like SCardDisconnect (this can make a scratch) can't be call since not implemented in the drivers. >> 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). Yes. >Regards, Andreas Moreover keep in mind more use of opensc is done more usefull and longtime the project will exist, So to give the possibility for all windows application using cryptographics to use opensc is interesting... François.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
