OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

pkcs11 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Identifier review.


So I've just completed a comparison between the identifiers in pkcs11/working/3-00-wd-01/pkcs11t.h and the identifier database and found some inconstancies. Most were typos (either in the database or in header) which I resolved in favor of the provided spec. There are a few identifiers that have not been added to the header yet. And there was once case where there were identifiers in the header that were not in the database. The spec they came from looks like it predated, or was very early in the database creation process. I've resolved all those issues (except identifiers that are not yet added to the header).

I then turned my attention to the various specs that we've approved, looking to see if we have identifiers that are not yet in the database.  I've found the following cases:

1. approved specs that added new identifiers, but did not get a number (and are not in the database).

2. approved specs that added new identifiers with a number, but aren't allocated in the database.

3. approved specs that added new identifier types and the new identifiers, but did not specify values for those new identifiers.

4. approved specs that added new identifier types and did add values for those new identifiers.

I'm planning on resolving these issues as follows:

cases 1 and 3: allocation new identifier values for these and publishing them to this list. We can discuss in our next meeting or here if we need to vote on them.

case 2: fortunately there is not conflict in the numbers in catagory 2. Since they are voted, approved specs I will simply allocate the values documented in the spec.

case 4: There is actually nothing fundamentally wrong with these values. I will add them to the database so that we can 1) track future changes to those values, and 2) make sure they make it into the header files.

Below is a summary of those identifiers by Spec in which they were found:

--------------------------------------------------------------------------------------------------------------------------------------------

SP800 Flexible Symmetric KDF (Darren Johnson)

Mechanisms
CKM_SP800_108_COUNTER_KDF
CKM_SP800_108_FEEDBACK_KDF
CKM_SP800_108_DOUBLE_PIPELINE_KDF

New Type (SP800 Types)
CK_SP800_108_ITERATION_VARIABLE
CK_SP800_108_OPTIONAL_COUNTER
CK_SP800_108_DKM_LENGTH
CK_SP800_108_BYTE_ARRAY

---------------------------------------------------

Profile Object (Bob Relyea)

Object
CKO_PROFILE

Attribute
CKA_PROFILE_ID

New Type (ProfilesID)
#define CKP_INVALID_ID           0x00000000UL
#define CKP_VENDOR               0x80000000UL
#define CKP_BASELINE_PROVIDER    0x00000001UL
#define CKP_EXTENDED_PROVIDER    0x00000002UL
#define CKP_AUTHENTICATION_TOKEN 0x00000003UL


-------------------------------------------------
Additional ECC Curves (Darren Johnson) ballot 3151

Mechanisms
CKM_EC_EDWARDS_KEY_PAIR_GEN
CKM_EC_MONTGOMERY_KEY_PAIR_GEN
CKM_EDDSA

KeyTypes
CKK_EC_EDWARDS
CKK_EC_MONTGOMERY

------------------------------------------------
AEAD (Bob Relyea) Minutes12042017

New Type (Message Flags)
#define CKF_END_OF_MESSAGE 0x00000001

Error
#define CKR_AEAD_DECRYPT_FAILED 0x00000042 (not allocated!)

------------------------------------------------
New Functions (Bob Relyea) Minutes12042017

New Type (Function Flags)
#define CKF_FORK_SAFE_INTERFACE    0x00000001UL

-----------------------------------------------
AES GCM SPEC (Bob Relyea) Minutes12042017

New Type (Generator Functions)
CKG_NO_GENERATE
CKG_GENERATE
CKG_GENERATE_COUNTER
CKG_GENERATE_RANDOM

-----------------------------------------------
C_SessionCancel (Darren Jonson) Minutes12042017

Mechanism flags
CKF_FIND_OBJECTS 0x00000040 (not allocated!)




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]