SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: two follow-ups for NV Index registry commit

Browse Source 
As per review comments on https://github.com/systemd/systemd/pull/33394

Follow-up for: 6e12c598d34eb9345d8c000f1abe790f4d79c5c5

(cherry picked from commit cc76554de0736ec5623635493cb238620c589da8)
This commit is contained in:
Lennart Poettering
2026-10-16 17:24:52 +01:00
committed by Luca Boccassi
parent 38a75c5433
commit 4cf713b8ab
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/TPM2_NVINDEX_ASSIGNMENTS.md
+1 -1
View File
@@ -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.
docs/TPM2_PCR_MEASUREMENTS.md
+1 -1
View File
@@ -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.