![Thales ProtectToolkit 5.9.1 Скачать руководство пользователя страница 75](http://html1.mh-extra.com/html/thales/protecttoolkit-5-9-1/protecttoolkit-5-9-1_installation-and-configuration-manual_1099198075.webp)
Chapter 4: ProtectToolkit Software Installation
If the compile fails, or the driver does not come up automatically (
hsmstate
fails), you will need to correct the
problem and then
cd /opt/ETpcihsm/src
and invoke
make(1)
as root. The
Makefile
in that directory has
some notes to help you get the driver compiled correctly.
To uninstall the PCie access provider manually
Use the
rpm(8)
command with the appropriate package name as a parameter.
# rpm -e PTKpcihsmK7
Signing the ProtectServer PCIe 2 Driver for UEFI Secure Boot
Red Hat Enterprise Linux 7 (RHEL 7) can be installed and run on systems where UEFI Secure Boot is enabled.
With Secure Boot enabled, the RHEL kernel requires all kernel modules, including device drivers, to be signed
by a key that is trusted by the EFI boot loader. If a module is not signed, it is prevented from loading at runtime
and the dependent device will not work.
To use ProtectServer PCIe 2 in a Secure Boot-enabled environment, the driver must be signed and trusted by
the OS and boot loader.
The following procedure includes:
>
Generating RSA signing keys and certificates
>
Signing the ProtectServer PCIe driver
>
Enrolling the signing public key into the system keyring
>
Loading the signed driver
NOTE
This procedure applies only to a CentOS 7 environment with UEFI Secure Boot
enabled. The steps have been tested on RHEL release 7.6.1810. The
mokutil
utility on
earlier versions of Red Hat might show inconsistent behavior. If you encounter problems,
upgrade your OS.
Steps may vary on other Linux platforms, but the general procedure is the same.
Prerequisites
>
UEFI Secure Boot must be enabled on the Linux system.
>
The ProtectServer PCIe 2 Access Provider must be installed.
The driver will fail to load and
service vkd status
may return
vkd is not running
.
System logs might display the error message
could not insert module vkd.ko: Required key not
available
. This appears because the driver module
vkd.ko
needs to be signed.
>
Driver signing requires that the following tools be available on the system:
Tool
Provided by
Package
Used on
Purpose
openssl
openssl
Build system
Generates public and private X.509 key pair
Thales ProtectServer HSM 5.9.1 ProtectServer HSM and ProtectToolkit Installation and Configuration Guide
2021-11-02 08:51:40-04:00 Copyright 2009-2021 Thales Group
75