On 2010/08/14 20:57, Martin Paljak wrote: Hi,
Thanks for your reply. See my comments inline. > Hello, > On Aug 12, 2010, at 5:23 AM, Nikolay Elenkov wrote: >> I am developing a (proprietary) dynamic card driver (Windows). I have the >> basics >> setup working, I can load and login. However I am having some troubles with >> locking (transactions). Any advice is much appreciated. > > For which card? Why not write an open source driver instead? Are you writing > a dynamic basic card driver (it's not ISO7816 or require SM for basic file > operations as well?) or a PKCS#15 emulation driver? It's a Java card running a proprietary PKI applet. There is no file structure, so it's a PKCS#15 emulation driver. > > If you have a proprietary library to work with, maybe you can change it so > that it would not lock the card itself? The library is used for other projects using the card (most notably a CSP), so I wouldn't like to maintain an 'OpenSC-only' version as well. > If the library does everything (up to the point of creating transaction) > then maybe it will not fit nicely at all into the OpenSC framework. What can be done to make it fit nicely? (besides re-writing all code to use OpenSC APIs for communicating with the card, that is) > Dynamic drivers are supposed to be used with cards that don't want to > "expose" their APDU commands and/or file structures. But I don't see why > hiding them makes it any better either. I tend to agree, but it's not my decision. > > If you need a dynamic driver to "hide" the secure messaging keys (?) then maybe you can look around in the secure messaging branch [1] for inspiration on how to use that with your card. Thanks, will check it out. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
