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 an option to unconditionally preserve luks keyfiles used for luks device setup #1983

Open
yacoob opened this issue Nov 30, 2024 · 0 comments

Comments

@yacoob
Copy link

yacoob commented Nov 30, 2024

From what I can see here, luks keyfiles (provided or generated) are only written to sysroot if clevis hasn't been configured. This makes the resulting setup brittle, if there's been both keyfile and clevis configured if the keyfiles have been generated by ignition itself. We end up with a luks device with two keys, one stored in tpm, the other being effectively unusable, as it was generated randomly, used, then discarded.

While we're at it: would it be possible to change the default location of the keyfiles to /etc/cryptsetup-keys.d/volumename.key to align with systemd defaults?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant