Martin Paljak wrote: > Hi Viktor. > > On 26.11.2009, at 20:55, Viktor TARASOV wrote: > >> for the Oberthur card I'm going to commit the PinPad support for PIN >> changing and unblocking. >> >> But before, I would like to know if there are any objections for >> the following changes to calls of do_change() and do_unblock() in >> opensc-explorer. >> > Why do pkcs15-tool --change-pin and --unblock-pin not work for you? I know > that the PIN input routines of pkcs15-tool don't consider pinpads currently, > but IMHO it is better to implement it and keep it there. > > opensc-tool, opensc-explorer, pkcs15-tool, pkcs15-crypt, pkcs15-init - there > are five "basic" commands in OpenSC, they should not duplicate functionality. >
OK, I see. This question was because I've started to test the card specific 'pinpad PIN verify' with opensc-explorer and afterwards, for 'pinpad unblock and change', have not looked for the other tools. I will use the 'high-level' ones. > For some cards, information set in the pkcs15-emulation layer would be useful > to the underlying card drivers, so better start from "above" and move to > lower levels. > ... like a 'pin policy', that is used at the low level, and can be taken from the PKCS#15 level. > Talking of PIN related API-s, there are a few places that still implement the > "old style API" of change_reference_data and verify instead of sc_pin_cmd. In > fact, new drivers have been added without the pin_cmd interface but the "old" > interface. > Viktor. -- Viktor Tarasov <viktor.tara...@opentrust.com> _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
