On Wed, 2011-06-08 at 17:31 +0200, Andre Zepezauer wrote: > On Wed, 2011-06-08 at 17:45 +0300, Martin Paljak wrote: > > Hello, > > > > > > On Wed, Jun 8, 2011 at 17:37, Andre Zepezauer > > <andre.zepeza...@student.uni-halle.de> wrote: > > >> More elegant indeed. Some nice documentation about the real meaning of > > >> the flag would also be nice. "most cards do almost ISO" to support > > >> pinpads. > > >> But not all support the status query... > > > > > > Maybe I'm wrong, but IMO Viktor had implemented the status query through > > > empty data field some time ago. So, there would be at least two cards > > > which does support it. > > > > > > > > There was discussion about it a few months ago, probably at the same > > time. The general consensus (also my personal opinion) seemed to be > > that it is safer not to probe the card, as there are several cards > > that don't support the convention and some even decrease the retry > > counter (like the buggy new ID-card in Estonia...) > > > > Even though many cards override pin_cmd, extra care should be taken to > > not accidentally block a PIN code, thus the feature (like a flag) > > should be set case-by-case. > > Would it be safe enough to set a specific flag in the drivers init > function? And if set, then the status query could be performed without > casing harm. > > Open questions: > * is it worth to make that effort
Some usage scenarios: Let pkcs11-tool -L show the following flags: CKF_USER_PIN_COUNT_LOW, CKF_USER_PIN_FINAL_TRY, CKF_USER_PIN_LOCKED Let pkcs11-tool -l show something like this: Logging into "My Token (PIN)". Please enter User PIN (*** FINAL TRY ***): _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
