From 4cf713b8abd6263d12cd6ce0bc66b102c04ab6c4 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 16 Oct 2026 09:07:48 +0200 Subject: [PATCH] docs: two follow-ups for NV Index registry commit As per review comments on https://github.com/systemd/systemd/pull/33394 Follow-up for: 6e12c598d34eb9345d8c000f1abe790f4d79c5c5 (cherry picked from commit cc76554de0736ec5623635493cb238620c589da8) --- docs/TPM2_NVINDEX_ASSIGNMENTS.md | 2 +- docs/TPM2_PCR_MEASUREMENTS.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/TPM2_NVINDEX_ASSIGNMENTS.md b/docs/TPM2_NVINDEX_ASSIGNMENTS.md index 3fcb27ba61..e3cdd40904 100644 --- a/docs/TPM2_NVINDEX_ASSIGNMENTS.md +++ b/docs/TPM2_NVINDEX_ASSIGNMENTS.md @@ -40,7 +40,7 @@ on the same system. Their base NV index may be changed at build time via the assignments. The `systemd-pcrlock` policy hashes are allocated dynamically at OS -installation time, one for each installed OS that uses `systemd-pcrlock` based +installation time, one for each installed OS that uses `systemd-pcrlock`-based disk encryption policies. An NV index is picked randomly from the subrange (retrying on collision), hence at most 24 such OSes can be installed on the same system. diff --git a/docs/TPM2_PCR_MEASUREMENTS.md b/docs/TPM2_PCR_MEASUREMENTS.md index aa1f590a03..809ea254f9 100644 --- a/docs/TPM2_PCR_MEASUREMENTS.md +++ b/docs/TPM2_PCR_MEASUREMENTS.md @@ -54,7 +54,7 @@ the NV index handle space. The NV index range to use for this is configurable at build time, so that downstreams have some flexibility to change this if they want. This uses the 0x01d10200 NV index as base by default (see [TPM NV Index Assignments by -systemd](/TPM2_NVINDEX_ASSIGNMENTS) for the NV index ranges systemd uses). To +systemd](/TPM2_NVINDEX_ASSIGNMENTS) for the NV index ranges systemd uses). To abstract the actual nvindex number away there's a naming concept, so that nvindexes are referenced by name string rather than number.