pkcs #11 cryptographic token interface current ...€¦ · web viewi also have some questions about...

SHA-1 and SHA-2 Updates proposal draft 1, 28, Aug 2016Author: Darren Johnson

I went a bit further than was originally discussed on the last call. I made 4 distict changes outlined below. I’m not dead set on including all of these updates, so if anyone things some of the changes should be rolled back, it is open for discussion.

Updates to existing content are all marked in red text below. All further updates (ie draft 2) will be done with change tracking enabled.

I also have some questions about SHA-512/t explained below. For the most part I left the SHA-512/t section untouched until those questions are addressed.

1) Updated SHA-384, SHA-512, SHA-512/224, SHA-512/256 and SHA-512/t with some text and tables that were already present in the SHA-224 and SHA-256 sections.

2) Changed the formatting of the “Definitions” section for SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256 and SHA-512/t so that they were consistent with the rest of the standard. We should probably considering adding this same change to the SHA3 proposal (as a editorial change) before it gets in to the standard.

3) I did not see any way to explicitly generate any of the SHA2 HMAC key types (where the SHA3 proposal has specific key generation mechanisms for this). So I backported this concept and introduced key generation mechanisms for the SHA-1 and SHA2 HMAC key types (ie. CKM_SHA224_KEY_GEN, CKM_SHA256_KEY_GEN…). Is there any reason not to make these changes in this proposal?

4) I hope people stop using SHA-1… but until we label SHA-1 as a legacy mechanism, we should probably try to keep it up to date with the other digests. So I updated SHA-1 to be in sync with SHA2 and SHA3. This is mostly a documentation exercise as I doubt any vendor will implement the SHA-1 additions. Is there any reason not to include these changes in this proposal?

SHA-512/t questionsWhy do we have these two mechanisms (CKM_SHA512_T_HMAC and CKM_SHA512_T_HMAC_GENERAL)?SHA-512/t by definition produces a truncated output. So why is there a “_GENERAL”? From the way the standard is currently written, the two mechanisms sound exactly the same.The value of “t” is used to define the initial digest value as well as the truncated digest out. So I guess I could understand the desire for a specific “t” value and still truncate the output beyond ⌈t/8⌉. If that is the intended goal, then shouldn’t CKM_SHA512_T_HMAC_GENERAL take two inputs; a “t” value and a HMAC output value? Which means CK_MAC_GENERAL_PARAMS would no longer work.

1.1 SHA-1Table 1, SHA-1 Mechanisms vs. Functions

Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA_1

CKM_SHA_1_HMAC_GENERAL

CKM_SHA_1_HMAC

CKM_SHA1_KEY_DERIVATION

CKM_SHA_1_KEY_GEN

1.1.1 DefinitionsThis section defines the key type “CKK_SHA_1_HMAC” for type CK_KEY_TYPE as used in the CKA_KEY_TYPE attribute of key objects.Mechanisms:

CKM_SHA_1 CKM_SHA_1_HMAC CKM_SHA_1_HMAC_GENERAL CKM_SHA1_KEY_DERIVATIONCKM_SHA_1_KEY_GENCKK_SHA_1_HMAC

1.1.2 SHA-1 digestThe SHA-1 mechanism, denoted CKM_SHA_1, is a mechanism for message digesting, following the Secure Hash Algorithm with a 160-bit message digest defined in FIPS PUB 180-2.It does not have a parameter.Constraints on the length of input and output data are summarized in the following table. For single-part digesting, the data and the digest may begin at the same location in memory.

Table 2, SHA-1: Data Length

Function Input length Digest lengthC_Digest any 20

1.1.3 General-length SHA-1-HMACThe general-length SHA-1-HMAC mechanism, denoted CKM_SHA_1_HMAC_GENERAL, is a mechanism for signatures and verification. It uses the HMAC construction, based on the SHA-1 hash function. The keys it uses are generic secret keys and CKK_SHA_1_HMAC.It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the length in bytes of the desired output. This length should be in the range 0-20 (the output size of SHA-1 is 20 bytes). Signatures (MACs) produced by this mechanism will be taken from the start of the full 20-byte HMAC output.

Table 3, General-length SHA-1-HMAC: Key And Data Length

Function Key type Data length Signature lengthC_Sign generic secret,

CKK_SHA_1_HMAC

any 0-20, depending on parameters

C_Verify generic secret, CKK_SHA_1_

HMAC

any 0-20, depending on parameters

1.1.4 SHA-1-HMACThe SHA-1-HMAC mechanism, denoted CKM_SHA_1_HMAC, is a special case of the general-length SHA-1-HMAC mechanism in Section 1.1.3.It has no parameter, and always produces an output of length 20.

1.1.5 SHA-1 key derivationSHA-1 key derivation, denoted CKM_SHA1_KEY_DERIVATION, is a mechanism which provides the capability of deriving a secret key by digesting the value of another secret key with SHA-1. The value of the base key is digested once, and the result is used to make the value of derived secret key. If no length or key type is provided in the template, then the key produced by this mechanism will be a

generic secret key. Its length will be 20 bytes (the output size of SHA-1). If no key type is provided in the template, but a length is, then the key produced by this mechanism

will be a generic secret key of the specified length. If no length was provided in the template, but a key type is, then that key type must have a well-

defined length. If it does, then the key produced by this mechanism will be of the type specified in the template. If it doesn’t, an error will be returned.

If both a key type and a length are provided in the template, the length must be compatible with that key type. The key produced by this mechanism will be of the specified type and length.

If a DES, DES2, or CDMF key is derived with this mechanism, the parity bits of the key will be set properly.If the requested type of key requires more than 20 bytes, such as DES3, an error is generated.This mechanism has the following rules about key sensitivity and extractability: The CKA_SENSITIVE and CKA_EXTRACTABLE attributes in the template for the new key can both

be specified to be either CK_TRUE or CK_FALSE. If omitted, these attributes each take on some default value.

If the base key has its CKA_ALWAYS_SENSITIVE attribute set to CK_FALSE, then the derived key will as well. If the base key has its CKA_ALWAYS_SENSITIVE attribute set to CK_TRUE, then the derived key has its CKA_ALWAYS_SENSITIVE attribute set to the same value as its CKA_SENSITIVE attribute.

Similarly, if the base key has its CKA_NEVER_EXTRACTABLE attribute set to CK_FALSE, then the derived key will, too. If the base key has its CKA_NEVER_EXTRACTABLE attribute set to CK_TRUE, then the derived key has its CKA_NEVER_EXTRACTABLE attribute set to the opposite value from its CKA_EXTRACTABLE attribute.

1.1.6 SHA-1 HMAC key generationThe SHA-1-HMAC key generation mechanism, denoted CKM_SHA_1_KEY_GEN, is a key generation mechanism for NIST’s SHA-1-HMAC.It does not have a parameter.The mechanism generates SHA-1-HMAC keys with a particular length in bytes, as specified in the CKA_VALUE_LEN attribute of the template for the key.

The mechanism contributes the CKA_CLASS, CKA_KEY_TYPE, and CKA_VALUE attributes to the new key. Other attributes supported by the SHA-1-HMAC key type (specifically, the flags indicating which functions the key supports) may be specified in the template for the key, or else are assigned default initial values.For this mechanism, the ulMinKeySize and ulMaxKeySize fields of the CK_MECHANISM_INFO structure specify the supported range of CKM_SHA_1_HMAC key sizes, in bytes.


Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA224

CKM_SHA224_HMAC

CKM_SHA224_HMAC_GENERAL

CKM_SHA224_RSA_PKCS

CKM_SHA224_RSA_PKCS_PSS


CKM_SHA224_KEY_GEN

1.2.1 DefinitionsThis section defines the key type “CKK_SHA224_HMAC” for type CK_KEY_TYPE as used in the CKA_KEY_TYPE attribute of key objects.Mechanisms:

CKM_SHA224 CKM_SHA224_HMAC CKM_SHA224_HMAC_GENERAL CKM_SHA224_KEY_DERIVATIONCKM_SHA224_KEY_GENCKK_SHA224_HMAC

1.2.2 SHA-224 digestThe SHA-224 mechanism, denoted CKM_SHA224, is a mechanism for message digesting, following the Secure Hash Algorithm with a 224-bit message digest defined in Error: Reference source not found.It does not have a parameter.Constraints on the length of input and output data are summarized in the following table. For single-part digesting, the data and the digest may begin at the same location in memory.



1.2.3 General-length SHA-224-HMACThe general-length SHA-224-HMAC mechanism, denoted CKM_SHA224_HMAC_GENERAL, is the same as the general-length SHA-1-HMAC mechanism except that it uses the HMAC construction based

on the SHA-224 hash function and length of the output should be in the range 0-28. The keys it uses are generic secret keys and CKK_SHA224_HMAC. FIPS-198 compliant tokens may require the key length to be at least 14 bytes; that is, half the size of the SHA-224 hash output.It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the length in bytes of the desired output. This length should be in the range 0-28 (the output size of SHA-224 is 28 bytes). FIPS-198 compliant tokens may constrain the output length to be at least 4 or 14 (half the maximum length). Signatures (MACs) produced by this mechanism will be taken from the start of the full 28-byte HMAC output.



CKK_SHA224_HMAC

Any 0-28, depending on parameters

C_Verify generic secret, CKK_SHA224_

HMAC


1.2.4 SHA-224-HMACThe SHA-224-HMAC mechanism, denoted CKM_SHA224_HMAC, is a special case of the general-length SHA-224-HMAC mechanism.It has no parameter, and always produces an output of length 28.

1.2.5 SHA-224 key derivationSHA-224 key derivation, denoted CKM_SHA224_KEY_DERIVATION, is the same as the SHA-1 key derivation mechanism in Section 12.21.5 except that it uses the SHA-224 hash function and the relevant length is 28 bytes.

1.2.6 SHA-224 HMAC key generationThe SHA-224-HMAC key generation mechanism, denoted CKM_SHA224_KEY_GEN, is a key generation mechanism for NIST’s SHA224-HMAC.It does not have a parameter.The mechanism generates SHA224-HMAC keys with a particular length in bytes, as specified in the CKA_VALUE_LEN attribute of the template for the key.The mechanism contributes the CKA_CLASS, CKA_KEY_TYPE, and CKA_VALUE attributes to the new key. Other attributes supported by the SHA224-HMAC key type (specifically, the flags indicating which functions the key supports) may be specified in the template for the key, or else are assigned default initial values.For this mechanism, the ulMinKeySize and ulMaxKeySize fields of the CK_MECHANISM_INFO structure specify the supported range of CKM_SHA224_HMAC key sizes, in bytes.


Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA256


Darren Johnson, 09/27/16,

How much effort should go in to formatting data and tables? Is this something our editors will take care of? Most of the tables all have the same layout/size. How much effort should be put in to maintaining that?

Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA256_HMAC


CKM_SHA256_KEY_GEN



1.3.2 SHA-256 digestThe SHA-256 mechanism, denoted CKM_SHA256, is a mechanism for message digesting, following the Secure Hash Algorithm with a 256-bit message digest defined in FIPS PUB 180-2.It does not have a parameter.Constraints on the length of input and output data are summarized in the following table. For single-part digesting, the data and the digest may begin at the same location in memory.



1.3.3 General-length SHA-256-HMACThe general-length SHA-256-HMAC mechanism, denoted CKM_SHA256_HMAC_GENERAL, is the same as the general-length SHA-1-HMAC mechanism in Section 1.1.3, except that it uses the HMAC construction based on the SHA-256 hash function and length of the output should be in the range 0-32. The keys it uses are generic secret keys and CKK_SHA256_HMAC. FIPS-198 compliant tokens may require the key length to be at least 16 bytes; that is, half the size of the SHA-256 hash output.It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the length in bytes of the desired output. This length should be in the range 0-32 (the output size of SHA-256 is 32 bytes). FIPS-198 compliant tokens may constrain the output length to be at least 4 or 16 (half the maximum length). Signatures (MACs) produced by this mechanism will be taken from the start of the full 32-byte HMAC output.



CKK_SHA256_HMAC


C_Verify generic secret, CKK_SHA256_

HMAC


1.3.4 SHA-256-HMACThe SHA-256-HMAC mechanism, denoted CKM_SHA256_HMAC, is a special case of the general-length SHA-256-HMAC mechanism in Section 1.3.3.It has no parameter, and always produces an output of length 32.

1.3.5 SHA-256 key derivationSHA-256 key derivation, denoted CKM_SHA256_KEY_DERIVATION, is the same as the SHA-1 key derivation mechanism in Section 1.1.5, except that it uses the SHA-256 hash function and the relevant length is 32 bytes.



Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA384


CKM_SHA384_HMAC


CKM_SHA384_KEY_GEN









CKK_SHA384_HMAC


C_Verify generic secret,CKK_SHA384_

HMAC






Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA512


CKM_SHA512_HMAC


CKM_SHA512_KEY_GEN









CKK_SHA512_HMAC



HMAC





1.6 SHA-512/224Table 16, SHA-512/224 Mechanisms vs. Functions

MechanismFunctions

Encrypt&

Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA512_224

CKM_SHA512_224_HMAC_GENERAL

CKM_SHA512_224_HMAC

CKM_SHA512_224_KEY_DERIVATION

CKM_SHA512_224_KEY_GEN

1.6.1 DefinitionsThis section defines the key type “CKK_SHA512_224_HMAC” for type CK_KEY_TYPE as used in the CKA_KEY_TYPE attribute of key objects.Mechanisms:

CKM_SHA512_224 CKM_SHA512_224_HMAC CKM_SHA512_224_HMAC_GENERAL CKM_SHA512_224_KEY_DERIVATIONCKM_SHA512_224_KEY_GENCKK_SHA512_224_HMAC

1.6.2 SHA-512/224 digestThe SHA-512/224 mechanism, denoted CKM_SHA512_224, is a mechanism for message digesting, following the Secure Hash Algorithm defined in FIPS PUB 180-4, section 5.3.6. It is based on a 512-bit message digest with a distinct initial hash value and truncated to 224 bits. CKM_SHA512_224 is the same as CKM_SHA512_T with a parameter value of 224.It does not have a parameter.Constraints on the length of input and output data are summarized in the following table. For single-part digesting, the data and the digest may begin at the same location in memory.

Table 17, SHA-512/224: Data Length


1.6.3 General-length SHA-512/224-HMACThe general-length SHA-512/224-HMAC mechanism, denoted CKM_SHA512_224_HMAC_GENERAL, is the same as the general-length SHA-1-HMAC mechanism in Section 1.1.3, except that it uses the HMAC construction based on the SHA-512/224 hash function and length of the output should be in the range 0-28. The keys it uses are generic secret keys and CKK_SHA512_224_HMAC. FIPS-198 compliant tokens may require the key length to be at least 14 bytes; that is, half the size of the SHA-512/224 hash output.It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the length in bytes of the desired output. This length should be in the range 0-28 (the output size of SHA-512/224 is 28 bytes). FIPS-198 compliant tokens may constrain the output length to be at least 4 or 14 (half the maximum length). Signatures (MACs) produced by this mechanism will be taken from the start of the full 28-byte HMAC output.



CKK_SHA512_224_HMAC



224_HMAC


1.6.4 SHA-512/224-HMACThe SHA-512-HMAC mechanism, denoted CKM_SHA512_224_HMAC, is a special case of the general-length SHA-512/224-HMAC mechanism.It has no parameter, and always produces an output of length 28.

1.6.5 SHA-512/224 key derivationThe SHA-512/224 key derivation, denoted CKM_SHA512_224_KEY_DERIVATION, is the same as the SHA-512 key derivation mechanism in section 2.25.5, except that it uses the SHA-512/224 hash function and the relevant length is 28 bytes.

1.6.6 SHA-512/224 HMAC key generationThe SHA-512/224-HMAC key generation mechanism, denoted CKM_SHA512_224_KEY_GEN, is a key generation mechanism for NIST’s SHA512/224-HMAC.It does not have a parameter.The mechanism generates SHA512/224-HMAC keys with a particular length in bytes, as specified in the CKA_VALUE_LEN attribute of the template for the key.The mechanism contributes the CKA_CLASS, CKA_KEY_TYPE, and CKA_VALUE attributes to the new key. Other attributes supported by the SHA512/224-HMAC key type (specifically, the flags indicating which functions the key supports) may be specified in the template for the key, or else are assigned default initial values.For this mechanism, the ulMinKeySize and ulMaxKeySize fields of the CK_MECHANISM_INFO structure specify the supported range of CKM_SHA512_224_HMAC key sizes, in bytes.

1.7 SHA-512/256Table 19, SHA-512/256 Mechanisms vs. Functions

MechanismFunctions

Encrypt&

Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA512_256

CKM_SHA512_256_HMAC_GENERAL

CKM_SHA512_256_HMAC

CKM_SHA512_256_KEY_DERIVATION

CKM_SHA512_256_KEY_GEN

1.7.1 DefinitionsThis section defines the key type “CKK_SHA512_256_HMAC” for type CK_KEY_TYPE as used in the CKA_KEY_TYPE attribute of key objects.

Mechanisms:CKM_SHA512_256 CKM_SHA512_256_HMAC CKM_SHA512_256_HMAC_GENERAL CKM_SHA512_256_KEY_DERIVATIONCKM_SHA512_256_KEY_GENCKK_SHA512_256_HMAC

1.7.2 SHA-512/256 digestThe SHA-512/256 mechanism, denoted CKM_SHA512_256, is a mechanism for message digesting, following the Secure Hash Algorithm defined in FIPS PUB 180-4, section 5.3.6. It is based on a 512-bit message digest with a distinct initial hash value and truncated to 256 bits. CKM_SHA512_256 is the same as CKM_SHA512_T with a parameter value of 256.It does not have a parameter.Constraints on the length of input and output data are summarized in the following table. For single-part digesting, the data and the digest may begin at the same location in memory.



1.7.3 General-length SHA-512/256-HMACThe general-length SHA-512/256-HMAC mechanism, denoted CKM_SHA512_256_HMAC_GENERAL, is the same as the general-length SHA-1-HMAC mechanism in Section 1.1.3, except that it uses the HMAC construction based on the SHA-512/256 hash function and length of the output should be in the range 0-32. The keys it uses are generic secret keys and CKK_SHA512_256_HMAC. FIPS-198 compliant tokens may require the key length to be at least 16 bytes; that is, half the size of the SHA-512/256 hash output.It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the length in bytes of the desired output. This length should be in the range 0-32 (the output size of SHA-512/256 is 32 bytes). FIPS-198 compliant tokens may constrain the output length to be at least 4 or 16 (half the maximum length). Signatures (MACs) produced by this mechanism will be taken from the start of the full 32-byte HMAC output.



CKK_SHA512_256_HMAC



256_HMAC


1.7.4 SHA-512/256-HMACThe SHA-512-HMAC mechanism, denoted CKM_SHA512_256_HMAC, is a special case of the general-length SHA-512/256-HMAC mechanism.It has no parameter, and always produces an output of length 32.

1.7.5 SHA-512/256 key derivationThe SHA-512/256 key derivation, denoted CKM_SHA512_256_KEY_DERIVATION, is the same as the SHA-512 key derivation mechanism in section 2.25.5, except that it uses the SHA-512/256 hash function and the relevant length is 32 bytes.

1.7.6 SHA-512/256 HMAC key generationThe SHA-512/256-HMAC key generation mechanism, denoted CKM_SHA512_256_KEY_GEN, is a key generation mechanism for NIST’s SHA512/256-HMAC.It does not have a parameter.The mechanism generates SHA512/256-HMAC keys with a particular length in bytes, as specified in the CKA_VALUE_LEN attribute of the template for the key.The mechanism contributes the CKA_CLASS, CKA_KEY_TYPE, and CKA_VALUE attributes to the new key. Other attributes supported by the SHA512/256-HMAC key type (specifically, the flags indicating which functions the key supports) may be specified in the template for the key, or else are assigned default initial values.For this mechanism, the ulMinKeySize and ulMaxKeySize fields of the CK_MECHANISM_INFO structure specify the supported range of CKM_SHA512_256_HMAC key sizes, in bytes.

1.8 SHA-512/tTable 22, SHA-512 / t Mechanisms vs. Functions

Functions

MechanismEncrypt

&Decrypt

Sign&

Verify

SR&

VR1

DigestGen. Key

/KeyPair

Wrap&

UnwrapDerive

CKM_SHA512_T

CKM_SHA512_T_HMAC_GENERAL

CKM_SHA512_T_HMAC

CKM_SHA512_T_KEY_DERIVATION

CKM_SHA512_T_KEY_GEN

1.8.1 DefinitionsThis section defines the key type “CKK_SHA512_T_HMAC” for type CK_KEY_TYPE as used in the CKA_KEY_TYPE attribute of key objects.Mechanisms:

CKM_SHA512_T CKM_SHA512_T_HMAC CKM_SHA512_T_HMAC_GENERAL CKM_SHA512_T_KEY_DERIVATIONCKM_SHA512_T_KEY_GENCKK_SHA512_T_HMAC

1.8.2 SHA-512/t digestThe SHA-512/t mechanism, denoted CKM_SHA512_T, is a mechanism for message digesting, following the Secure Hash Algorithm defined in FIPS PUB 180-4, section 5.3.6. It is based on a 512-bit message digest with a distinct initial hash value and truncated to t bits.

It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the value of t in bits. The length in bytes of the desired output should be in the range of 0-⌈ t/8⌉, where 0 < t < 512, and t <> 384.Constraints on the length of input and output data are summarized in the following table. For single-part digesting, the data and the digest may begin at the same location in memory.


Function Input length Digest lengthC_Digest any ⌈t/8⌉, where 0 < t < 512, and t <> 384

1.8.3 General-length SHA-512/t-HMACThe general-length SHA-512/t256-HMAC mechanism, denoted CKM_SHA512_T_HMAC_GENERAL, is the same as the general-length SHA-1-HMAC mechanism in Section 1.1.3, except that it uses the HMAC construction based on the SHA-512/t hash function and length of the output should be in the range 0 – ⌈t/8⌉, where 0 < t < 512, and t <> 384.

1.8.4 SHA-512/t-HMACThe SHA-512/t-HMAC mechanism, denoted CKM_SHA512_T_HMAC, is a special case of the general-length SHA-512/t256-HMAC mechanism.It has a parameter, a CK_MAC_GENERAL_PARAMS, which holds the value of t in bits. The length in bytes of the desired output should be in the range of 0-⌈t/8⌉, where 0 < t < 512, and t <> 384.

1.8.5 SHA-512/t key derivationThe SHA-512/t256 key derivation, denoted CKM_SHA512_T_KEY_DERIVATION, is the same as the SHA-512 key derivation mechanism in section 2.25.5, except that it uses the SHA-512/t256 hash function and the relevant length is ⌈t/8⌉ bytes, where 0 < t < 512, and t <> 384.

1.8.6 SHA-512/t HMAC key generationThe SHA-512/t-HMAC key generation mechanism, denoted CKM_SHA512_T_KEY_GEN, is a key generation mechanism for NIST’s SHA512/t-HMAC.It does not have a parameter.The mechanism generates SHA512/t-HMAC keys with a particular length in bytes, as specified in the CKA_VALUE_LEN attribute of the template for the key.The mechanism contributes the CKA_CLASS, CKA_KEY_TYPE, and CKA_VALUE attributes to the new key. Other attributes supported by the SHA512/t-HMAC key type (specifically, the flags indicating which functions the key supports) may be specified in the template for the key, or else are assigned default initial values.For this mechanism, the ulMinKeySize and ulMaxKeySize fields of the CK_MECHANISM_INFO structure specify the supported range of CKM_SHA512_T_HMAC key sizes, in bytes.

Header file changes:

Add the following to pkcs11t.h

Under /* the following mechanism types are defined: */#define CKM_SHA_1_KEY_GEN 0x00000XXXUL#define CKM_SHA224_KEY_GEN 0x00000XXXUL#define CKM_SHA256_KEY_GEN 0x00000XXXUL

Darren Johnson, 09/28/16,

Need a reference to a mechanism parameter. If only “t” is required for input, than CK_MAC_GENERAL_PARAMS will suffice. But if we need to input an HMAC length, then we need another CK_ULONG input.

#define CKM_SHA384_KEY_GEN 0x00000XXXUL#define CKM_SHA512_KEY_GEN 0x00000XXXUL#define CKM_SHA512_224_KEY_GEN 0x00000XXXUL#define CKM_SHA512_256_KEY_GEN 0x00000XXXUL#define CKM_SHA512_T_KEY_GEN 0x00000XXXUL

pkcs #11 cryptographic token interface current ...€¦ · web viewi also have some questions about...

Documents