Hello. All executables that are provided in OpenSC (and use libopensc internally, which means pkcs11-tool is an exception) should behave the same way and accept the same options, to some extent.
I made some changes and also documented some notes on [1], what should be done as minimum is: - provide manpages for all commands installed on Linux - use the common util.c card connection code (detecting the reader with a card, waiting for card, connecting with a reader name instead of array index), netkey-tool and westcos-tool are ones that don't do it (and both should have active maintainers?) - don't duplicate functionality that *should* be available via pkcs15-init or pkcs15-tool or similar common tools. This includes generating keys for example, unless there really is a reason. Do you have other observations or suggestions for harmonizing the usage experience of the tools? [1] http://www.opensc-project.org/opensc/wiki/ToolsAndUtilities -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
