bootc-dev / bootc-dev/bootc

LUKS volumes need configurable password and/or recovery keys

Offen
#477 2 Kommentare 4 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area/install
Vorherrschende Sprache
Rust
Sterne
2.3k
Forks
230
Ø Merge
3 T. 12 Std.
Gemergte PRs (30 T.)
38

Beschreibung

See problems described in #476 and #421 for context.

The `bootc install to-disk --block-setup tpm2-luks` feature needs to provision either a systemd-cryptenroll recovery key or a default/backup password for the root LUKS volume. This is a necessity to ensure systems can be booted and users are not locked out when TPM PCR hashes change (they can and will change over time as the system is maintained).

Sometimes TPM PCR hashes change -- this is an expected and intended thing that happens on any system used over a period of time since they measure aspects of the system (which can change over time). Solely relying on the TPM to unlock root volumes is risky and exposes users to a lockout/non bootable situation without a recovery key or password. A bad and completely avoidable experience.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by reading issues #476 and #421, then inspect the implementation of `bootc install to-disk --block-setup tpm2-luks`. Determine how the root LUKS volume is provisioned and where a systemd-cryptenroll recovery key or default/backup password could be configured. Done means users have a non-TPM recovery method and systems remain bootable when TPM PCR hashes change.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
linux, rust
Bereich
operating-systems, security
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.