On 14.09.2009, at 10:42, Andreas Jellinghaus wrote: > for many cards we have a special tool so we access low level functions > of the card like formatting, debuggging, getting firmware version etc. > are there any such functions that could require such a low level tool? > or does the card driver everything, so no need for that?
Actually, if the functions overlap, instead of getting many-many small utilities with almost similar functionality, we might extend opensc- tool (or pkcs15-init?) to do most of the functions depending on the card type and if there is some really exotic stuff, opensc-tool -- special-mycard-erase would be a better option, IMHO, than mycard-tool with only option --erase-special. Of course it makes sense to split it on source code file level but a single interface for the user feels simpler at least to me. Just like the idea of OpenSC is to support via a single project / API / library a bunch of cards instead every card making its own "mycard-pkcs11.so", the same should be followed in command line utilities. What do you think? -- Martin Paljak http://martin.paljak.pri.ee +372.515.6495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
