Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config option to configure systemd-cryptenroll PCRs #476

Open
jmpolom opened this issue Apr 18, 2024 · 0 comments
Open

Add config option to configure systemd-cryptenroll PCRs #476

jmpolom opened this issue Apr 18, 2024 · 0 comments
Labels
area/install Issues related to `bootc install`

Comments

@jmpolom
Copy link

jmpolom commented Apr 18, 2024

Right now bootc uses the naive systemd-cryptenroll default PCR selection of 7 when binding a LUKS volume. This is not ideal as shim package updates or version disagreement between installation and installed environment will cause the PCR 7 hash to change thus prevent unlocking of the LUKS root volume.

Beyond the obvious implications that broken boot is a very bad user experience, use of PCR 7 only is not necessarily a best practice when using TPM to unlock encrypted partitions. Users will most certainly need control over the PCR configuration and the systemd-cryptenroll defaults are really not intended as production solutions (they are a rather plain default that might work in some cases).

Either an install configuration or CLI option is needed to allow configuration of the TPM PCRs that the LUKS volume is bound to.

@cgwalters cgwalters added the area/install Issues related to `bootc install` label Apr 25, 2024
cgwalters pushed a commit to cgwalters/bootc that referenced this issue Nov 5, 2024
cgwalters pushed a commit to cgwalters/bootc that referenced this issue Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to `bootc install`
Projects
None yet
Development

No branches or pull requests

2 participants