[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [pkcs11] Groups - pkcs11-base-v2.40-loginuser-v1-changes.pdf uploaded
This is a much needed addition to the PKCS#11 API. I must of missed it but how is the "user name" created in a token in the first place? Is there a corresponding update to the C_SetPIN operation?Thanks,Mark JosephP6R, IncFrom: Tim Hudson <tjh@cryptsoft.com>
To: <pkcs11@lists.oasis-open.org>
Sent: 4/12/2017 2:15 PM
Subject: [pkcs11] Groups - pkcs11-base-v2.40-loginuser-v1-changes.pdf uploaded Submitter's message
Note: everywhere that C_Login is referenced elsewhere in the text it is changed to C_Login or C_LoginUser - allowing that either can be used.
A word version with those changes applied can be uploaded if anyone wants to look at it.
-- Tim Hudson
Document Name: pkcs11-base-v2.40-loginuser- v1-changes.pdf
Description
C_LoginUser text to match mailing list proposal.
This is simply the same as C_Login only allowing the username to be
provided as a separate parameter instead of being jammed into the PIN
parameter (current practice).
Download Latest Revision
Public Download Link
Submitter: Tim Hudson
Group: OASIS PKCS 11 TC
Folder: Working Drafts
Date submitted: 2017-04-12 14:15:15
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]