mirror of
https://github.com/linuxboot/heads.git
synced 2025-01-18 18:57:04 +00:00
6923fb5e20
-coreboot support of TPM v2.0 (shared config for TPM2 support across all 4 previous variations) -swtpm set to be launched under TPM v2.0 mode under board config -Documentation file under each board.md softlinks to qemu-coreboot-fbwhiptail-tpm1.md (which has been generalized) This is skeleton for TPM v2 integration under Heads ------------- WiP TODO: - libcurl cannot be built as a tpm2-tools dependency as of now not sure why. curl currently needs to be added in board config to be built - Note: tpm-reset (master and here) needs some review, no handle of no tpm use case. Caller is responsible to not call it otherwise does nothing - init tries to bind fd and fails currently - Note: Check if whiptail is different of fbwhiptail in clearing screen. As of now every clear seems to be removed, still whiptail clears previous console output - When no OS' /boot can be mounted, do not try to TPM reset (will fail) - seal-hotpkey is not working properly - setting disk unlock key asks for TPM ownership passphrase (sealing in NV requires ownership, but text is misleading user as if reowning TPM) - We should cache input, feed tpm behind the scene and wipe passphrase and state clearly that this is TPM disk unlock kye passphrase. - primary key from TPM2 is invalid most of the time from kexec-select-boot and verifying global hashes but is setuped correctly at disk unlock key setup - would be nice to take advantage of bash function tracing to understand where we are for debugging purposes, code takes ash in consideration only - tpmr says it implements nv calls but actually doesn't. Removing those falsely wrapped functions would help. - Implementing them would be better - REVIEW TODOS IN CODE - READD CIRCLECI CONFIG Current state: - TPM unseal works without disk unlock key and generates TOTP properly (was missing die condition at unseal to not produce always good TOTP even if invalid) - TPM disk encryption key fails. Hypothesis is that sealing with USB drivers loaded and measures in inconsistent with sealed with/without. - TPM disk unsealing happens without USB modules being loaded in non-HOTP setup. This fails. - Current tests are with fbwhiptail (no clear called so having traces on command line of what happens) - Testing with HOTP implementation for sealing/unsealing since that forces USB module loads on each boot to remove this from failing possibilities |
||
|---|---|---|
| .. | ||
| coreboot-4.8.1 | ||
| coreboot-4.11 | ||
| coreboot-4.13 | ||
| coreboot-4.14 | ||
| coreboot-4.17 | ||
| flashrom-b1f858f65b2abd276542650d8cb9e382da258967 | ||
| linux-4.14.62 | ||
| linux-4.19.139 | ||
| linux-5.4.69 | ||
| linux-5.5-openpower | ||
| linux-5.10.5 | ||
| busybox-1.32.0.patch | ||
| cryptsetup2-2.3.3.patch | ||
| cryptsetup-1.7.3.patch | ||
| dropbear-2016.74.patch | ||
| gpg2-2.2.10.patch | ||
| gpg2-2.2.21.patch | ||
| gpg-1.4.21.patch | ||
| kexec-2.0.22.patch | ||
| libassuan-2.5.1.patch | ||
| libassuan-2.5.3.patch | ||
| libgcrypt-1.8.3.patch | ||
| libgcrypt-1.8.6.patch | ||
| libgpg-error-1.37.patch | ||
| libksba-1.3.5.patch | ||
| libksba-1.4.0.patch | ||
| lvm2-2.02.168.patch | ||
| pciutils-3.5.4.patch | ||
| tpm2-tools-5.2.patch | ||
| tpm2-tss-3.2.0.patch | ||
| util-linux-2.29.2.patch | ||