It is highly recommended to upgrade to this version as it implements a defense-in-depth strategy for broken TPMs. See Upgrade sectpmctl for how to upgrade without reinstallation.
Warning: It is highly recommended to install sectpmctl on a fresh system installation as you could run into problems when the tpm2-tools or efitools can't be executed successfully on your device. Create at least a backup of your data before installation. If you already installed DKMS modules, it is probably necessary to rebuild them after installing sectpmctl to have them signed.
We want to secure Debian >= 12 and Ubuntu >= 22.04 installations with LUKS and TPM2. Please read this README carefully before installation.
We assume an installation with LVM and encryption. Don't create a recovery key in the Debian or Ubuntu installation, set only the LUKS password. An automated Ubuntu Server preseed installation is supported (but currently undocumented) in which the Secure Boot keys are applied in the subiquity phase while the LUKS key is sealed into the TPM in the first boot after. Other Linux distributions can probably be supported in future releases.
If you are not using the TPM + password option you should supply a BIOS start password. Without either a BIOS start password or TPM + password, the device would boot up to the login screen and someone could try to read out the memory or find a bug in the login screen to recover the LUKS key.
Either way, you should also supply a BIOS admin password.
Dual booting Windows is not recommended and has never been tested with sectpmctl. The risk is that Windows will update the Secure Boot DBX database which will prevent the successful unlocking of the LUKS key. In such case, you need the recovery key and need to redo the sectpmctl installation, see recovery for more information.
It is recommended to only have one LUKS slot in use before installation, which is mostly slot 0. sectpmctl will additionally use slot 5 to store the TPM key.
You can easily test the installation with virt-manager on a Ubuntu 22.04 host and a supported guest system. When creating a new VM you need to
configure the VM before it starts automatically. In the overview select OVMF_CODE_4M.secboot.fd as firmware and then add a new TPM emulated TIS 2.0 device. After the installation of the system, you can start installing sectpmctl.
For transparency, the tpm2-tools commands for session encryption, provisioning, TOFU, seal, unseal, and password change are documented at the end of this README. The commands for using Secure Boot are standard except for using the TPM as a key store for the db signing key. Take a look at the source code to see how that works. If you are wondering, yes the PK and KEK keys are not stored at all in the current implementation, they are simply not needed in this decentralized implementation.
Using a splash screen and the TPM + Password option does not work correctly. If that happens you need to enter the password blindly.
The rise of the faulTPM attack has shown that it is necessary to think about security more in-depth. The attack allows to fully break the TPM of relative modern AMD CPUs. The mitigation strategy is to make use of key derivation as the TPM can't be trusted. Using key derivation lets the attacker require to brute force at least the password of the TPM + password option. That also means that TPM-only protection is not recommended at all. The default in this README is therefore the TPM + password option. The goal on broken TPM systems is to provide at least the same security as if a software-only encryption had been used instead of TPM + password.
As faulTPM had shown, all key material can be extracted from the TPM without authorization. The proposed mitigation from the authors is to use the TPM + password option, together with a KDF and appending the password to the TPM secret which opens LUKS:
Sealing
A LUKS_SECRET is computed randomly
User enters TPM_PASSWORD
PWD_HASHED = argon2(TPM_PASSWORD)
LUKS_SECRET is sealed in the TPM with PWD_HASHED instead of TPM_PASSWORD as authorization
LUKS will be encryted by LUKS_SECRET + TPM_PASSWORD
LUKS will use argon2 for encryption internally as wellUnsealing
User enters TPM_PASSWORD
PWD_HASHED = argon2(TPM_PASSWORD)
LUKS_SECRET is unsealed from the TPM with PWD_HASHED as authorization
LUKS will be decryped by LUKS_SECRET + TPM_PASSWORD
LUKS will use argon2 for decryption internally as wellThe catch is that if the TPM is completely broken, then the LUKS_SECRET is known to the attacker. But that won't be sufficient to decrypt, because the original password needs to be known. The attacker has to brute force the password with argon2id as KDF. Therefore, sectpmctl with TPM + password option on a vulnerable system is at least as strong as a software-only encryption without a TPM at all.
Currently, sectpmctl reads out the argon2id parameters from the LUKS2 partition itself and uses the same parameters to compute PWD_HASHED:
LUKS2 places internal hard limits on the argon2id parameters (Memory <= 1GB, CPUs <= 4). A future release of sectpmctl could be able to support much stronger parameters than LUKS2 offers without sacrificing the ability to decrypt on slower devices, as there are two LUKs keys, one for the TPM (which may have stronger argon2id settings) and the high entropy recovery key (which may use the default argon2id LUKS settings).
Setting the authorization password to a random value without storing it enhances security because the lockout hierarchy can not be
modified without a password after TPM provisioning. This hierarchy also prevents accidental use of the tpm2_clear command. If you know
that you need access to the lockout hierarchy, you should remove the option --forgetlockout from the sudo sectpmctl tpm provisioning
command in the installation section. If this option is not set, the lockout password is stored in
/var/lib/sectpmctl/keys/lockout.pwd. You can change this option also at a later time by reinstalling sectpmctl again (see the
full recovery section for how to do it).
Setting the endorsement authorization password to a random value without storing it enhances privacy because the endorsement hierarchy
can be used to uniquely identify your device. If you know that you need access to the endorsement hierarchy, you should remove the
option --setforgetendorsement from the sudo sectpmctl tpm provisioning command in the installation section. When this
option is not set, the endorsement authorization password will be empty. You can change this option also at a later time by reinstalling
sectpmctl again (see the full recovery section for how to do it).
When installing the sectpmctl bootloader, Microsoft keys are automatically uploaded to the Secure Boot database for your safety. An option exists to suppress the uploading of the Microsoft keys. Together with a BIOS admin password, hardware without an UEFI OptionROM requirement, like laptops with integrated graphics, gains the protection that no other operating system can boot. This should probably also increase security on another end. When sectpmctl is installed without a TPM password, the device will boot unattended (if there is no BIOS startup password or if it has been removed). Such systems would be able to execute bootloaders signed by Microsoft, so it could be possible that an attacker can boot software that tries to read out the system memory to get access to the LUKS key which is still in the DDR RAM for some seconds. Disabling the booting of any other bootloader will prevent this relatively simple attack. And even if the attacker can put his own or Microsoft keys into the Secure Boot database, sectpmctl rejects to boot in the first place because PCR 7 would then be invalid.
When this option is used together with a BIOS administrator password and the TPM + password option, a stolen device becomes useless for the thief as it won't boot any other operating system anymore.
But this option is highly dangerous. When it is used on a device (typically servers and desktops or laptops with a dedicated PCI graphic card) where the hardware strictly requires the Microsoft keys you will for sure at least semi-brick or completely brick the device.
Do NOT use the --withoutmicrosoftkeys option of the sectpmctl boot install tool when:
Do use the option with care when:
In the case of graphic cards for example, when omitting the Microsoft keys, the screen will stay black when you power on the device. It will not even work when the operating system is finished booting. If you are (very) lucky, you could maybe navigate blindly in the BIOS to disable Secure Boot. Then, on the next start, the graphic card will function again. You can then restore the Secure Boot factory keys and enable Secure Boot again. Another option is maybe to buy a very old graphics card or a CPU with integrated graphics to recover. On laptops, it is not possible to switch to another graphic card for booting and the brick could be final, immutable, and can maybe never be recovered.
The sbctl project has a FAQ for the Microsoft keys.
This option will only work when you enter the Clear Mode in the Secure Boot BIOS settings, that is when the complete Secure Boot database is empty. If you enter the Setup Mode (only the PK key is cleared instead of the complete Secure Boot database) this option won't work.
Differentiation of the Microsoft Windows and the Microsoft UEFI key is currently not done. Either both or none will be installed.
You have been warned, it is highly possible to destroy your system without being able to fix it! Do an internet search before using this option and ask somebody who might know if it could work. If you brick your device you are on your own. Use at your own risk!
You can either install the prebuild version or follow the build instructions:
wget https://github.com/telekom-mms/tpmsbsigntool/releases/download/0.9.4-2-3/tpmsbsigntool_0.9.4-2-3_amd64.deb
sudo dpkg -i tpmsbsigntool_0.9.4-2-3_amd64.deb
sudo apt install -yfIt is recommended to build tpmsbsigntool on Ubuntu 22.04 for compatibility with newer versions including Debian. If you don't need backward compatibility, you can compile it on newer systems as well.
sudo apt install -y git devscripts debhelper-compat gcc-multilib binutils-dev libssl-dev \
openssl pkg-config automake uuid-dev help2man gnu-efi tpm2-openssl
git clone https://github.com/telekom-mms/tpmsbsigntool.git
cd tpmsbsigntool
git checkout 0.9.4-2-3
debuild -b -uc -us
cd ..
sudo dpkg -i ./tpmsbsigntool_0.9.4-2-3_amd64.deb
sudo apt install -yfAlternatively you can build the package with docker (which needs to be able to run with user permissions):
git clone https://github.com/telekom-mms/tpmsbsigntool.git
cd tpmsbsigntool
git checkout 0.9.4-2-3
./docker.sh
sudo dpkg -i ./tpmsbsigntool_0.9.4-2-3_amd64.deb
sudo apt install -yf
cd ..You can either download the prebuild version or follow the build instructions. The installation is done later in the installation section.
wget https://github.com/telekom-mms/sectpmctl/releases/download/1.2.0/sectpmctl_1.2.0-1_amd64.debIt is recommended to build sectpmctl on Ubuntu 22.04 for compatibility with newer versions including Debian. If you don't need backward compatibility, you can compile it on newer systems as well.
sudo apt install -y debhelper efibootmgr efitools sbsigntool binutils mokutil dkms systemd udev \
util-linux gdisk openssl uuid-runtime tpm2-tools fdisk git devscripts build-essential pkg-config \
libargon2-dev
git clone https://github.com/telekom-mms/sectpmctl.git
cd sectpmctl
git checkout 1.2.0
make package_build
cd ..Alternatively you can build the package with docker (which needs to be able to run with user permissions):
git clone https://github.com/telekom-mms/sectpmctl.git
cd sectpmctl
git checkout 1.2.0
./docker.sh
cd ..
mv sectpmctl/sectpmctl_1.2.0-1_amd64.deb .Warning: After removing grub and shim there is no alternative than to complete the installation, otherwise your system will most probably not boot anymore.
Your BIOS has to be in Secure Boot Clear Mode. That means that your BIOS needs to have Secure Boot enabled and that all keys are cleared. You
can do so by entering your BIOS, enabling Secure Boot, and finding inside the Secure Boot section the button to Clear all keys. Set a BIOS
administrator password as well.
We never came across a BIOS that does not offer a way to enter Secure Boot Setup Mode. If your BIOS supports listing all keys, after entering the clear mode, the number of keys of all databases should be zero. If your Secure Boot settings are grayed out, you most probably have to set a BIOS administrator password first.
First check if your Secure Boot is enabled and cleared by executing these two commands:
mokutil --sb-state
efi-readvarThe output should look like this:
user@laptop:~$ mokutil --sb-state
SecureBoot disabled
Platform is in Setup Mode
user@laptop:~$ efi-readvar
Variable PK has no entries
Variable KEK has no entries
Variable db has no entries
Variable dbx has no entries
Variable MokList has no entriesAs sectpmctl will provision your TPM in a minimal way, it is required to start the installation with a cleared TPM. That can be achieved in three ways:
echo 5 | sudo tee /sys/class/tpm/tpm0/ppi/request and reboot.Be warned that if you put already keys into the TPM, they will be lost by the clearing.
Be also warned that when a TPM lockout password is set and you try to clear the TPM with software commands and enter a wrong lockout password, there will be a time penalty until you can try again. The above three ways to clear should allow you to clear the TPM even when you entered the wrong lockout password.
To check if the TPM is in a good state enter:
sudo tpm2_getcap properties-variableThe output should look like this:
user@laptop:~$ sudo tpm2_getcap properties-variable
...
lockoutAuthSet: 0
...
inLockout: 0
...The command which will be executed later while installing (sectpmctl tpm provisioning) should run successfully with a cleared TPM and the
the output should look like this:
user@laptop:~$ sudo sectpmctl tpm provisioning
START PROVISIONING
## TPM CLEAR
## SET DICTIONARY LOCKOUT SETTINGS
## CREATE AND SET THE LOCKOUTAUTH VALUE
## CREATE PERSISTENT PRIMARY OWNER SRK AT 0x81000100
## CREATE PERSISTENT PRIMARY OWNER NODA SRK AT 0x81000101The provisioning will by default set a random lockout password which is stored in /var/lib/sectpmctl/keys/lockout.pwd, set sane dictionary
attack lockout time penalty settings and create two TPM primary keys, one with the dictionary attack lockout flag (DA) and one without (NODA).
This installation will use the options --forgetlockout and --setforgetendorsement. See
Security and privacy options for more information.
The following DA lockout values are set:
Unsealing the LUKS key while booting without TPM + password and signing of kernels and kernel modules is done by using the NODA primary key to not break updates in case of a dictionary lockout situation. When using the TPM + password option, the unsealing while booting is done with the DA key, while keep using the NODA key for signing kernels and kernel modules.
All generated keys, passwords, or serialized keys are stored in /var/lib/sectpmctl/keys.
It is highly recommended to upgrade. This version contains better security for broken TPMs and enables support for Ubuntu release upgrades.
Download or build this version by following build sectpmctl. Then install it:
sudo dpkg -i sectpmctl_1.2.0-1_amd64.debNote: It is not sufficient to only install the latest release of sectpmctl. The sectpmctl tpm install command needs to be executed to perform
the upgrade. See the TPM resealing only section for how to do it.
Execute this command to see which version is currently applied:
sudo sectpmctl tpm get-installed-version
| Installed version | Applied version | Action |
|---|---|---|
| <= 1.1.5 | <= 1.1.5 | build sectpmctl, sudo dpkg -i sectpmctl_1.2.0-1_amd64.deb and upgrade to 1.2.0 |
| 1.2.0 | <= 1.1.5 | upgrade to 1.2.0 |
| 1.2.0 | 1.2.0 |
First, upgrade to sectpmctl 1.2.0. See the upgrade sectpmctl section.
When starting a release upgrade from Ubuntu 22.04 to a newer version, configuration file changes made by sectpmctl probably lead to the question if you keep the currently installed versions or replace the files with the package maintainer version:
/etc/initramfs-tools/initramfs.conf/etc/dkms/framework.confThe initramfs-tools-core initramfs.conf file had been changed by older versions of sectpmctl. This change is not done anymore, but it could
still be on your system. The release upgrade will ask if you want to keep the currently installed version (N, O or keep) or replace it
with the package maintainer version (Y, I or replace). If you did customizations yourself to this file, you should keep the currently
installed version (N, O or keep), otherwise select replace with the package maintainer version (Y, I or replace).
The dkms framework.conf did not support config snippets until Ubuntu 22.10. Therefore sectpmctl needed to modify framework.conf on Ubuntu
22.04. The release upgrade will ask if you want to keep the currently installed version (N, O or keep) or replace it with the package
maintainer version (Y, I or replace). If you did customizations yourself to this file, you should keep the currently installed version
(N, O or keep), otherwise select replace with the package maintainer version (Y, I or replace).
sectpmctl and the release upgrade will boot and work correctly even if you miss selecting which version of these files to keep. Anyhow, it is recommended fixing these two files after the release upgrade reboot by executing the following commands, except you modified them manually:
sudo apt install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" initramfs-tools-core
sudo apt install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" dkmsUpgrades are working out of the box starting from sectpmctl 1.2.0 and Ubuntu 22.10. No actions are required.
Important note: The current implementation seals the LUKS key not only to the Secure Boot PCR values and optionally to a password but also to the LUKS header. That means that if the LUKS header is modified after installation, the system will not boot anymore without the recovery key. That is for example the case when another secret key is added to the encrypted root partition. It is highly recommended to not add other LUKS keys after installation, otherwise, a recovery has to be done which is described in the recovery section below.
Note: If the kernel signing certificate of Debian or Ubuntu changes in the future, you can temporarily allow the use of kernels that can not
yet be checked. In such a case, a newer version of sectpmctl will include the new certificates for the check. To allow unsigned and unchecked
kernels you need to edit /etc/sectpmctl/boot.conf and set SKIP_UNSIGNED_KERNELS to false. Secure Boot lockdown is automatically enforced
as sectpmctl adds lockdown=integrity to the kernel command line, see /var/lib/sectpmctl/kernel_extra_options. See
Debian and Ubuntu for more information.
# 1. Point of no return, you need to complete at least until the following reboot command
sudo apt remove --allow-remove-essential "grub*" "shim*"
sudo dpkg -i sectpmctl_1.2.0-1_amd64.deb
sudo apt install -yf
# 2. TPM Provisioning
# optionally disable swap while keys are created
sudo swapoff -a
sudo sectpmctl tpm provisioning --forgetlockout --setforgetendorsement
# 3. Cleanup leftovers from grub, shim, and windows with efibootmgr
while [[ $(efibootmgr | grep -c -m 1 "Windows Boot Manager") -gt 0 ]]
do
entryId=$(efibootmgr -v | grep -m 1 -i "Windows Boot Manager" | sed -e 's/^Boot\([0-9]\+\)\(.*\)$/\1/')
sudo efibootmgr -q -b "${entryId}" -B
done
while [[ $(efibootmgr | grep -c -m 1 "ubuntu") -gt 0 ]]
do
entryId=$(efibootmgr -v | grep -m 1 -i "ubuntu" | sed -e 's/^Boot\([0-9]\+\)\(.*\)$/\1/')
sudo efibootmgr -q -b "${entryId}" -B
done
while [[ $(efibootmgr | grep -c -m 1 "debian") -gt 0 ]]
do
entryId=$(efibootmgr -v | grep -m 1 -i "debian" | sed -e 's/^Boot\([0-9]\+\)\(.*\)$/\1/')
sudo efibootmgr -q -b "${entryId}" -B
done
while [[ $(efibootmgr | grep -c -m 1 "SECTPMCTL Bootloader") -gt 0 ]]
do
entryId=$(efibootmgr -v | grep -m 1 -i "SECTPMCTL Bootloader" | sed -e 's/^Boot\([0-9]\+\)\(.*\)$/\1/')
sudo efibootmgr -q -b "${entryId}" -B
done
# 4. Now migrate the boot partition to root, the following partition table is assumed, change all
# references according to your device and partition names and numbers:
# $DISK -> /dev/vda (the disk)
# $EFIPARTITION -> /dev/vda1 (EFI-System, vfat, partition type 1)
# $BOOTPARTITION -> /dev/vda2 (boot partition, ext4)
# $LUKSPARTITION -> /dev/vda3 (encrypted root partition)
sudo umount /boot/efi
sudo umount /boot
sudo mkdir /oldboot
sudo mount /dev/$BOOTPARTITION /oldboot
sudo cp -rp /oldboot/* /boot/
sudo umount /oldboot
sudo rmdir /oldboot
sudo dd if=/dev/zero of=/dev/$EFIPARTITION bs=1M
sudo dd if=/dev/zero of=/dev/$BOOTPARTITION bs=1M
sudo fdisk /dev/$DISK
# delete partition $BOOTPARTITION (e.g. vda2)
# delete partition $EFIPARTITION (e.g. vda1)
# create new parttion $EFIPARTITION (e.g. vda1)
# startsector same as startsector of old $EFIPARTITION
# lastsector same as lastsector of old $BOOTPARTITION
# remove signature: YES
# change type of partition $EFIPARTITION (e.g. vda1)
# type nr: 1 (EFI-System)
# write and quit
sudo mkfs.vfat /dev/$EFIPARTITION
sudo blkid -s UUID -o value /dev/$EFIPARTITION
# copy the UUID of /dev/$EFIPARTITION, something like: 00A5-1112
sudo vi /etc/fstab
# remove /boot entry from fstab
# change the old UUID of /boot/efi to the copied new UUID of the blkid output
sudo systemctl daemon-reload
sudo mount /boot/efi
# 5. Install the bootloader
sudo sectpmctl boot install
# TODO: Describe how to reinstall or rebuild all installed or build DKMS kernel
# modules to have them resigned.
# After this reboot your current LUKS password is still required
sudo reboot
# 6. Install the LUKS TPM implementation
# optionally disable swap while keys are created
sudo swapoff -a
# Now your machine has its own set of Secure Boot keys, test it. The test may
# fail if the TPM support is incomplete, like on some ACER devices. See
# 'Bugs and problems found' in this README.
sudo sectpmctl boot test
# Install the LUKS TPM key. Enter your current LUKS key when asked.
cat > install_tpm.sh <<__EOT
#! /bin/bash
echo -n "Enter TPM Password: "
read -sr tpmpwda
echo
echo -n "Enter TPM Password again: "
read -sr tpmpwdb
echo
if [[ "x\${tpmpwda}" == "x\${tpmpwdb}" ]]; then
sudo sectpmctl tpm install --setrecoverykey --password "\${tpmpwda}"
else
echo "Passwords don't match. Exit"
exit 1
fi
__EOT
chmod +x install_tpm.sh
./install_tpm.sh
rm install_tpm.sh
# STORE THE PRINTED RECOVERY KEY NOW!!!
# SCROLL UP A BIT IF IT GET'S OUT OF SIGHT!!!
# Reboot to test the installation
sudo reboot
# If the BIOS won't boot sectpmctl or shows "Secure Boot violation",
# please try to select sectpmctl from the BIOS boot menu (F12, ESC).
# If that works, but the system won't boot automatically, enter the BIOS
# and try to modify the boot order. Maybe another hard disk has priority.
# If you can't find sectpmctl, try all boot entries.The sectpmctl tpm install command will print out the recovery key. Store this key in a safe location. Without this key, you will lose all your
data when the TPM breaks or when accessing your hard disk on another machine. You have been warned!
The recovery key will be printed first, then the bootloader is updated. It can happen that the recovery key is not visible after the
installation. Then you need to scroll up a bit to see it. The recovery key is built by eight groups with eight characters from 0 to 9 and
a to f which sums up to 256bit. If this is too long you can decrease the number of groups or the group length with the sectpmctl tpm
options --recoverygroups and --recoverygrouplength. To create a shorter 192bit recovery key you can do so with 8 groups and a group length
of 6.
After a reboot, the LUKS partition should decrypt after typing the TPM password. The installation is complete.
You can then do some bootloader configuration by editing /etc/sectpmctl/boot.conf. Currently, a splash screen should not be activated. It
is disabled by default. The kernel option quiet is supported but disabled as well by default. It is also possible to configure a fixed set of
kernel options in the file /var/lib/sectpmctl/kernel_extra_options. Remember to update the bootloader afterward by executing
sudo sectpmctl boot updatefollowed by a reboot. You can also use the bootctl command for basic tasks. Do not use bootctl install as sectpmctl boot will handle the
installation and signing of the bootloader. To list the bootable kernels enter:
sudo bootctl listBy default, only kernels signed by Canonical or Debian are considered to be shown in the boot list. Unsigned kernels are ignored for safety
reasons. If you want to have support for all kernels, you can edit /etc/sectpmctl/boot.conf and set SKIP_UNSIGNED_KERNELS to false. Update
the bootloader with sectpmctl boot update afterward.
If the TPM password is lost or needs to be changed, see the recovery section. Currently, it requires the recovery key.
Kernel or kernel module updates will not create any problems. Whenever a kernel is installed or a DKMS module is updated or installed, the corresponding hooks are called to automatically sign the kernel and/or kernel modules in a very similar way as DKMS and grub are doing updates.
No userspace application except bootloaders should be able to cause any problems. It is better to not install any other bootloader. The UEFI specification allows for many bootloaders to be installed in parallel. No other bootloader will overwrite sectpmctl but most probably change the boot order. In such case, you can enter the boot menu of your BIOS (often the F12 key or such) and select sectpmctl again as boot entry. You can do it also permanently by using the efibootmgr command line although it could be a bit of a fiddle.
It seems that BIOS updates on Lenovo Thinkpads won't cause problems as they seem to keep the Secure Boot database and won't reset the TPM. All tested BIOS updates done so far did not result in preventing unsealing.
On the other hand on Gigabyte an X570S AERO motherboard, the Secure Boot database seems to be reset during BIOS update, with the result that the recovery password needs to be entered on the next boot and sectpmctl needs to be installed again.
If you know that Secure Boot and TPM stay stable there should be no problem in updating, otherwise, keep your recovery password within reach. In a future version, binding to PCR 0 and handling BIOS updates could be implemented. That requires either integration with fwupdatemgr or the execution of a command in front of the BIOS update.
After installing sectpmctl, a TPM-backed Secure Boot db key to sign kernels and kernel modules is stored in a serialized form in
/var/lib/sectpmctl/keys/db.obj. It is used by the tpmsbsigntool tool, which is based on openssl. The password for that key is stored in
/var/lib/sectpmctl/keys/db.pwd. The password is currently needed as the TPM2 openssl integration does not support binding keys to PCR values
yet. If it would, the TPM-backed signing key could only be used from within the sectpmctl secured system and the password would not be needed
anymore.
You normally don't need to use the db key manually. DKMS and kernel hooks are integrated and execute the sign commands automatically
for every kind of apt upgrade. Two helper scripts, which behave like sbsign and kmodsign, are located in /usr/lib/sectpmctl/scripts. They
show how to sign things manually:
A kmodsign wrapper is available at sectpmctl-kmodsign-wrapper. It is a config package that replaces the original kmodsign binary with a wrapper that calls tpmkmodsign internally, for example, to support the maintenance of commercial antivirus applications or such.
Please read the helper scripts before manually using them as they have specific needs for rewriting parameters.
It is also possible to prevent the signing of kernel modules by editing this file: /var/lib/tpmsbsigntool/tpmkmodsign_blocklist.conf
The full recovery needs to be done when the system does not boot without using the recovery key. That is the case when:
sectpmctl tpm provisioning)The Secure Boot database and TPM can be restored by following these steps:
You can omit the --setrecoverykey option in the sectpmctl tpm install command to keep your current recovery key.
TPM resealing needs to be done when either the system will boot correctly but sectpmctl needs to be updated or when the TPM password is lost or needs to be changed:
sectpmctl tpm install)Note: You need to boot the system by entering the recovery key in case of a lost TPM password.
Execute this command to reseal the TPM:
cat > install_tpm.sh <<__EOT
#! /bin/bash
echo -n "Enter TPM Password: "
read -sr tpmpwda
echo
echo -n "Enter TPM Password again: "
read -sr tpmpwdb
echo
if [[ "x\${tpmpwda}" == "x\${tpmpwdb}" ]]; then
sudo sectpmctl tpm install --setrecoverykey --password "\${tpmpwda}"
else
echo "Passwords don't match. Exit"
exit 1
fi
__EOT
chmod +x install_tpm.sh
./install_tpm.sh
rm install_tpm.shYou can omit the --setrecoverykey option in the sectpmctl tpm install command to keep your current recovery key.
The following persistent handles are created after provisioning and installation. The keyed hash is using one of the two parent objects.
| Handle | Object |
|---|---|
| 0x81000100 | Parent object with DA |
| 0x81000101 | Parent object with NODA |
| 0x81000102 | Keyed hash of LUKS key |
| PCR | Description |
|---|---|
| 0 | BIOS |
| 1 | BIOS Config |
| 2 | Option ROM |
| 3 | Option ROM Config |
| 4 | Bootloaders and EFI Blobs |
| 5 | GPT Partition Table |
| 6 | Resume Events (seems not to work on Linux) |
| 7 | SecureBoot State |
| 8-13 | GRUB and systemd Bootloader |
| 14 | shim Bootloader MOK and sectpmctl |
| PCR | value |
|---|---|
| 7 | Secureboot state |
| 14 | No MOK, LUKS header |
The LUKS header is measured into PCR 14 while sealing at installation time and while unsealing by the initrd. It has a special purpose. After unsealing the LUKS key in the initrd, PCR14 is extended with a random value. That blocks a second unsealing without having to extend a more meaningful register like PCR 7.
The optimal measurements:
| PCR 7 |
|---|
| initially zero |
| Secure Boot state |
| Secure Boot db |
| EV_SEPARATOR |
| db cert of sectpmctl |
| PCR 14 |
|---|
| initially zero (no shim, no MOK) |
| LUKS header |
PCR 14 is completely under control, while PCR 7 measurements might vary after the EV_SEPARATOR event, see Lenovo P15 Gen 2 laptop NVidia Problem for such a problematic case.
To see which measurements have been done for PCR 7, execute sudo tpm2_eventlog /sys/kernel/security/tpm0/binary_bios_measurements and
search for PCRIndex: 7 entries.
Currently, the following restrictions are applied:
Allow every kernel to boot -> Allow only, but all, kernels signed by the custom db key (PCR 7).
In a future version, more restrictions should be applied:
Allow every kernel to boot -> Allow only, but all, kernels signed by the custom db key (PCR 7) -> Resrict all db signed kernels to a finite list of kernels (PCR 7+4) -> Restrict this list to only the latest N kernels to prevent downgrade attacks (probably by using NV).
The commands used by sectpmctl are shown in the following sections. They can be executed standalone in an installation in which sectpmctl is not installed.
Performing TPM provisioning is required for advanced usage. The TPM has to be partitioned and secured. This implementation does not make use
of the endorsement key, some users want to disable this hierarchy anyway for privacy reasons. It also doesn't set passwords for the owner
hierarchy because that will sooner or later create problems with software that simply would not allow using an owner password, tpm2-topt for
example. The root user would be able to create new primary keys or even delete them, but that should not break security. Only the lockout
authorization is set by default.
The two public keys tpm_owner.pub and tpm_owner_noda.pub play an important role. They are used for session encryption, but more
importantly, they build the foundation of the TOFU principle. These public keys are used to establish a TPM session when unsealing in the
initrd. If the corresponding private key is not inside the TPM, then the communication is directly rejected. The public key is copied into the
initrd and of course, signed by Secure Boot so that manipulation of the public key won't boot. Deleting the private key in the TPM or using a
different TPM also won't boot. Only when the initrd finds the private keys created at provisioning time together with the initrds public key,
the encrypted session is established.
# Clear the TPM
tpm2_clear
# Set lockout values
tpm2_dictionarylockout --max-tries=32 --recovery-time=600 --lockout-recovery-time=1800 \
--setup-parameters
# The lockout authorization password is stored in plain text inside the encrypted root partition
tpm2_changeauth --object-context=lockout "high entropy password"
# Create the first primary key with DA flag, store the public key for TOFU
tpm2_createprimary --hierarchy=o --key-algorithm=rsa --key-context=prim.ctx
tpm2_evictcontrol --hierarchy=o --object-context=prim.ctx "0x81000100"
tpm2_readpublic --object-context="0x81000100" --serialized-handle="tpm_owner.pub"
# Create the second primary key with NODA flag, store the public key for TOFU
tpm2_createprimary --hierarchy=o --key-algorithm=rsa --key-context=prim_noda.ctx \
--attributes="fixedtpm|fixedparent|sensitivedataorigin|userwithauth|restricted|decrypt|noda"
tpm2_evictcontrol --hierarchy=o --object-context=prim_noda.ctx "0x81000101"
tpm2_readpublic --object-context="0x81000101" --serialized-handle="tpm_owner_noda.pub"When a session is established for sealing or unsealing, the public keys from the provisioning are used
# The tpm_owner_noda private key is available in the TPM
tpm2_startauthsession --policy-session --session="session.ctx" --key-context="tpm_owner_noda.pub"
tpm2_sessionconfig "session.ctx"
# -> Session-Attributes: continuesession|decrypt|encrypt# Example if the tpm_owner_noda private key is not available in the TPM
tpm2_startauthsession --policy-session --session="session.ctx" --key-context="tpm_owner_noda.pub"
# -> ERROR: Esys_StartAuthSession(0x18B) - tpm:handle(1):the handle is not correct for the use# Hash the TPM password
TPM_PASSWORD="mytpmpassword"
echo -n 12345678123456781234567812345678 > saltfile
TPM_HASHED_PASSWORD="$(sectpmctl hash --salt saltfile --time 4 --memory 1000000 --cpus 4 "${TPM_PASSWORD}")"
# Generate the TPM key
echo randomLuksSecret > LUKS_KEY_FILE
# Foresee or read the PCR values into "pcr_values.dat"
tpm2_pcrread "sha256:7,14" --output="pcr_values.dat"
# Create trial PCR with authvalue policy session
tpm2_startauthsession --session="trialsession.ctx"
tpm2_policypcr --session="trialsession.ctx" --pcr-list="sha256:7,14" \
--pcr="pcr_values.dat" --policy="pcr.policy"
tpm2_policyauthvalue --session="trialsession.ctx" --policy="pcr.policy"
tpm2_flushcontext "trialsession.ctx"
# Connect encrypted to the TPM with key enforcement (TOFU)
tpm2_startauthsession --policy-session --session="session.ctx" --key-context="tpm_owner.pub"
tpm2_sessionconfig "session.ctx"
# -> Session-Attributes: continuesession|decrypt|encrypt
# Seal the TPM key with TPM_HASHED_PASSWORD as authorization
tpm2_create --session="session.ctx" --hash-algorithm=sha256 --public="pcr_seal_key.pub" \
--private="pcr_seal_key.priv" --sealing-input="LUKS_KEY_FILE" \
--parent-context="0x81000100" --policy="pcr.policy" --attributes="fixedtpm|fixedparent" \
--key-auth="hex:${TPM_HASHED_PASSWORD}"
tpm2_flushcontext "session.ctx"
# Remove current object in handle, may fail if empty
tpm2_evictcontrol --object-context="0x81000202" --hierarchy=o 2> /dev/null > /dev/null
tpm2_load --parent-context="0x81000100" --public="pcr_seal_key.pub" \
--private="pcr_seal_key.priv" --name="pcr_seal_key.name" --key-context="pcr_seal_key.ctx"
# Store secret
tpm2_evictcontrol --object-context="pcr_seal_key.ctx" "0x81000202" --hierarchy=o
# Add unhashed password to TPM key
echo -n "${TPM_PASSWORD}" >> LUKS_KEY_FILE
# Use LUKS_KEY_FILE as the LUKS key file# Hash the TPM password
TPM_PASSWORD="mytpmpassword"
echo -n 12345678123456781234567812345678 > saltfile
TPM_HASHED_PASSWORD="$(sectpmctl hash --salt saltfile --time 4 --memory 1000000 --cpus 4 "${TPM_PASSWORD}")"
tpm2_startauthsession --policy-session --session="session.ctx" --key-context="tpm_owner.pub"
tpm2_sessionconfig "session.ctx"
# -> Session-Attributes: continuesession|decrypt|encrypt
tpm2_policypcr --session="session.ctx" --pcr-list="sha256:7,14"
tpm2_policyauthvalue --session="session.ctx"
# Unseal the TPM key with TPM_HASHED_PASSWORD as authorization
tpm2_unseal --auth="session:session.ctx+hex:${TPM_HASHED_PASSWORD}" --object-context="0x81000202" > LUKS_KEY_FILE
tpm2_flushcontext "session.ctx"
# Prevent a second unsealing
tpm2_pcrextend "14:sha256=0000000000000000000000000000000000000000000000000000000000000000"
# Add unhashed password to TPM key
echo -n "${TPM_PASSWORD}" >> LUKS_KEY_FILE
# Use LUKS_KEY_FILE as the LUKS key fileA future release could implement authorized policies for advanced features:
When many TPM (policy) sessions are created and not freed after use, a kernel bug could be triggered. When that happens, the TPM will not answer any more to commands. The output of dmesg will then show problems. The expected behavior is that tpm2 commands will return an error code. Therefore a timeout has been implemented in the key tool to prevent endless waiting. To prevent this problem at boot time (the sessions seem not be cleared automatically on booting) all TPM sessions are flushed before unsealing in the initrd.
During the unseal at boot time the kernel may load (some additional) kernel modules.
If this module loading results in a modification to the TPM PCR registers - especially while sectpmctl is doing the unsealing - the TPM will
return the error code TPM_RC_PCR_CHANGED, which prevents the unsealing of the LUKS partition.
To solve this problem a loop is implemented to simply retry unsealing 5 times with a sleep of 2 seconds in between. It seems to be difficult to have a stable parsing of this specific error code, therefore the loop is triggered on all TPM errors at boot time.
First to know is that you have to set a BIOS administrator password. Otherwise, the Secure Boot settings are grayed out and cannot be changed.
An installation on an ACER Swift 3 SF314-42 and an ACER Nitro AN515-45 laptop, both caused this problem:
--skipdbx option in
the sectpmctl boot install command. Skipping the DBX db is safe if no multi-boot is used and no Microsoft certificate is in the PCR 7 chain or
if the --withoutmicrosoftkeys option is used. See
Lenovo P15 Gen 2 laptop NVidia Problem for more information. When the --skipdbx option
is used and another system is installed at a later time, restore the Secure Boot factory keys from inside the BIOS to restore the
DBX db before installation of the new OS.An installation on an ACER Swift 3 SF314-42 caused the following problems only once and then never again:
efi-updatevar -d 0 db.echo 5 | sudo tee /sys/class/tpm/tpm0/ppi/request and remove
the tpm2_clear call in /usr/lib/sectpmctl/scripts/sectpmctl-tpm./usr/lib/sectpmctl/scripts/sectpmctl-tpm.These tools can be used to read the current Secure Boot and TPM settings:
mokutil --sb-state
efi-readvar
sudo tpm2_getcap properties-variableInside the BIOS, sectpmctl might be shown as the boot entry "*".
Be careful with BIOS updates. They may delete the Secure Boot database which then makes use of a recovery necessary.
This device provides a BIOS option to let the primary graphics be provided by the internal or the dedicated NVidia card. The PCR 7 measurement is different with this two options:
| PCR 7 measurements with internal graphics |
|---|
| Secure Boot state |
| Secure Boot db |
| EV_SEPARATOR |
| db cert of sectpmctl |
| PCR 7 measurements with dedicated graphics |
|---|
| Secure Boot state |
| Secure Boot db |
| EV_SEPARATOR |
| Microsoft UEFI CA |
| db cert of sectpmctl |
In the case of the dedicated graphics a problem arises: It is not possible to distinguish between booting the sectpmctl bootloader and booting a
compromised bootloader which is signed with the Microsoft UEFI CA and which then boots the sectpmctl bootloader, as the NVidia card option
forces the Microsoft UEFI CA into the boot chain. This problem can be solved in a future version by binding to PCR 7 together with PCR 4. For
now, it is suggested to select the internal graphics option before using the sectpmctl tpm install command. The command prime-select can
then be used to select the dedicated graphic card.
1.2.0
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.0
Every piece of information or code in this repository is written and collected with the best intentions in mind. We do not warrant that it is complete, correct, or that it is working on your platform. We provide everything as is and try to fix bugs and security issues as soon as possible. Use at your own risk.