Breadcrumbs

u.trust GP HSM PKCS#11 Configuration

  1. Create the directory /etc/utimaco/PKCS11. Locate the Utimaco PKCS#11 configuration file in your SecurityServer directory, Linux/x86-64/Crypto_APIS/PKCS11_R3/sample. Copy the Utimaco PKCS#11 configuration file cs_pkcs11_R3.cfg into the /etc/utimaco/PKCS11 directory.

# mkdir /etc/utimaco/PKCS11
# cd <install directory>/Software/Linux/x86-64/Crypto_APIs/PKCS11_R3/sample # cp
cs_pkcs11_R3.cfg /etc/utimaco/PKCS11 # cd /etc/utimaco/PKCS11

  1. Edit the cs_pkcs11_R3.cfg file and make the appropriate changes to it.

[Global]
# For unix:
Logpath = /tmp
# Loglevel (0 = NONE; 1 = ERROR; 2 = WARNING; 3 = INFO; 4 = TRACE)
Logging = 1
Keepalive = true
# Set the Device to connect with
[CryptoServer]
# Device specifier
Device = <HSM_IP>

cs_pkcs11_R3.cfg

For more information regarding the commands and command parameters, please
check the u.trust GP HSM 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 = 288@<HSM IP address> Hardware (LAN) HSM
OR
Device = /dev/cs2.0 Hardware (PCIe) HSM

To make your testing easier, you can enable the PKCS#11 log file.
That can be enabled by editing the Logging Loglevel. Set the LogPath and Logging
Loglevel to 1. For testing you may want to increase it to 4.
The added LogPath points to a writable directory, not to a file.
If you encounter problems, check the log file named cs_pkcs11_R3.log in the
LogPath defined directory. When you are done testing, you should change Logging
to 1 or 2. This will limit the logging to only critical and important messages.