Configs

Option to update the provisioning data like Expected Decrypted data, Initialization Vector for Wrapping, Application Root Keys,etc... More...

Collaboration diagram for Configs:

Macros
#define	PH_KEYSTORE_CONFIG_APP_ROOT_KEY_AES128_BIT   0x00A1U
	Updates the existing AES 128-Bit Application root key used during Initialization of Hardware based KeyStore. More...
#define	PH_KEYSTORE_CONFIG_APP_ROOT_KEY_AES256_BIT   0x00A2U
	Updates the existing AES 256-Bit Application root key used during Initialization of Hardware based KeyStore. More...
#define	PH_KEYSTORE_CONFIG_DERIV_MSG   0x00A3U
	Updates the existing Derivation message used for opening a Session or wrapping key during Initialization of Hardware based KeyStore. More...
#define	PH_KEYSTORE_CONFIG_EXPECTED_DEC_DATA   0x00A4U
	Expected Updates the existing Expected Decryption Data used for opening a Session or wrapping key during Initialization of Hardware based KeyStore. More...
#define	PH_KEYSTORE_CONFIG_WRAP_IV   0x00A5U
	Updates the existing Initialization Vector (WIV) used for opening a Session or wrapping key during Initialization of Hardware based KeyStore. More...

Detailed Description

Option to update the provisioning data like Expected Decrypted data, Initialization Vector for Wrapping, Application Root Keys,etc...

Macro Definition Documentation

PH_KEYSTORE_CONFIG_APP_ROOT_KEY_AES128_BIT

#define PH_KEYSTORE_CONFIG_APP_ROOT_KEY_AES128_BIT   0x00A1U

Updates the existing AES 128-Bit Application root key used during Initialization of Hardware based KeyStore.

Note

• Using this configuration, the key will be stored in the DataParams for further Provisioning of Fixed or ASymmetric Keys.
• Updating the Application root key will not provision the key in hardware. Application Root Key configured will be used from next operations.

PH_KEYSTORE_CONFIG_APP_ROOT_KEY_AES256_BIT

#define PH_KEYSTORE_CONFIG_APP_ROOT_KEY_AES256_BIT   0x00A2U

Updates the existing AES 256-Bit Application root key used during Initialization of Hardware based KeyStore.

Note

• Using this configuration, the key will be stored in the DataParams for further Provisioning Fixed or ASymmetric Keys.
• Updating the Application root key will not provision the key in hardware. Application Root Key configured will be used from next operations.

PH_KEYSTORE_CONFIG_DERIV_MSG

#define PH_KEYSTORE_CONFIG_DERIV_MSG   0x00A3U

Updates the existing Derivation message used for opening a Session or wrapping key during Initialization of Hardware based KeyStore.

Note

• Should be 24 bytes.
• Using this configuration, the information will be stored in the DataParams.
• Updating the Initialization Vector will not perform activities of Key Provisioning. Initialization Vector configured will be used from next operations.

PH_KEYSTORE_CONFIG_EXPECTED_DEC_DATA

#define PH_KEYSTORE_CONFIG_EXPECTED_DEC_DATA   0x00A4U

Expected Updates the existing Expected Decryption Data used for opening a Session or wrapping key during Initialization of Hardware based KeyStore.

Note

• Should be 24 bytes.
• Using this configuration, the information will be stored in the DataParams.
• Updating the Initialization Vector will not perform activities of Key Provisioning. Initialization Vector configured will be used from next operations.

PH_KEYSTORE_CONFIG_WRAP_IV

#define PH_KEYSTORE_CONFIG_WRAP_IV   0x00A5U

Updates the existing Initialization Vector (WIV) used for opening a Session or wrapping key during Initialization of Hardware based KeyStore.

Note

• Should be 16 bytes.
• Using this configuration, the information will be stored in the DataParams.
• Updating the Initialization Vector will not perform activities of Key Provisioning. Initialization Vector configured will be used from next operations.