Am Donnerstag 28 Januar 2010 14:56:43 schrieb Viktor TARASOV:
> Ok, for a while, I'll commit proposal from Andreas.
>
I fixed the text a bit. If I understood you right, the slot
needs the PUK for a login, and the purpose is to change the
PIN, right?
how does that relate to other new option in opensc.conf
right before that:
# User PIN unblock style
# none: PIN unblock is not possible with PKCS#11 API;
# set_pin_in_unlogged_session: C_SetPIN() in unlogged
session:
# PUK is passed as the 'OldPin' argument of the
C_SetPIN() call.
# set_pin_in_specific_context: C_SetPIN() in the
CKU_SPECIFIC_CONTEXT logged session:
# PUK is passed as the 'OldPin' argument of the
C_SetPIN() call.
# init_pin_in_so_session: C_InitPIN() in CKU_SO logged
session:
# User PIN 'UNBLOCK' is protected by SOPIN. (PUK ==
SOPIN).
# # Actually this style works only for the PKCS15
contents without SOPIN.
# # For those with SOPIN, this mode will be usefull for
the cards without
# # modes 00 and 01 of ISO command 'RESET RETRY
COUNTER'. --vt
#
# Default: none
# user_pin_unblock_style = set_pin_in_unlogged_session;
haveing several mechanism related to the same issue seems strange to me.
will this new slot replace that old mechanism? or how do they mix?
Regards, Andreas
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
