Configuration of Utimaco PKCS#11 Module
-
Create an
/etc/utimacodirectory. -
Locate the Utimaco PKCS#11 configuration file in your SecurityServer directory,
./u.trust_anchor_product_bundle-x.x.x/Software/Linux/Crypto_APIs/PKCS11_R3/sample. Copy the Utimaco PKCS#11 configuration filecs_pkcs11_R3.cfgto the/etc/utimacodirectory. -
Make the appropriate changes to the
cs_pkcs11_R3.cfgfile.
|
cs_pkcs11_R3.cfg |
|
For more information regarding the commands and command parameters, see the Utimaco SecurityServer documentation. The device may be a u.trust GP HSM (PCIe or LAN) device. The device line will follow one of these patterns, based on the HSM form factor:
Device = 4001@<HSM IP address> Hardware (LAN) HSM
or
Device = /dev/cs2.0 Hardware (PCIe) HSM
To make testing easier, enable the PKCS#11 log file by editing the Logging Loglevel. Set LogPath and Logging Loglevel to 1. For testing, you can increase them to 4.
The LogPath points to a writable directory, not to a file.
If you encounter problems, check the log file cs_pkcs11_R3.log in the directory specified under LogPath. During testing, change the Logging Loglevel to 1 or 2. This will limit the logging to only critical messages.
-
Set up the
CS_PKCS11_R3_CFGenvironment variable.
export CS_PKCS11_R3_CFG=/etc/utimaco/cs_pkcs11_R3.cfg
Initializing a PKCS#11 Slot
Create users SO (Security Officer) and USR (the Crypto user) and initialize a slot.
The slot must be initialized using the p11tool2.
First, create the SO using p11tool2. Then, using the p11tool2 command, initialize the Slot you want to use and the slot user, as shown below.
-
# ./p11tool2 slot=<slot no.> Label=<token label> Login=ADMIN,ADMIN.key InitToken=<SO pin>
Initialize the SO user.
-
# ./p11tool2 slot=<slot no.> LoginSO=<SO pin> InitPin=<Cryptouser pin>
Ensure the Utimaco GP HSM is accessible from the partner product control plane.