Using lanzaboote with LUKS is no different than using ordinary NixOS with LUKS. Adding tpm on top of that is then just a matter of enabling systemd initrd and using systemd-cryptenroll to mess with the key slots, and the man page for that program is pretty descriptive.
The directions are basically: Use lanzaboote, enable systemd initrd, finally use systemd-cryptenroll to enroll a TPM2 based key for the drive. Both lanzaboote and systemd initrd are what I would call experimental
Originally created by @ryan4yin on GitHub (Dec 1, 2023).
Related to:
- https://github.com/nix-community/lanzaboote
- https://www.reddit.com/r/NixOS/comments/xrgszw/nixos_full_disk_encryption_with_tpm_and_secure/
- Using lanzaboote with LUKS is no different than using ordinary NixOS with LUKS. Adding tpm on top of that is then just a matter of enabling systemd initrd and using systemd-cryptenroll to mess with the key slots, and the man page for that program is pretty descriptive.
- The directions are basically: Use lanzaboote, enable systemd initrd, finally use systemd-cryptenroll to enroll a TPM2 based key for the drive. Both lanzaboote and systemd initrd are what I would call experimental
Secure Boot signed all efi images, and it do not store other secrets in /boot, so it's safe to left /boot un-crypted(do not append any secret keys into initrd in this scenario!).
@ryan4yin commented on GitHub (Dec 2, 2023):
Secure Boot Enabled: https://github.com/ryan4yin/nix-config/commit/7c61a588086644d77f6aaaa061b61b4488eb4c61
Secure Boot signed all efi images, and it do not store other secrets in /boot, so it's safe to left /boot un-crypted(do not append any secret keys into initrd in this scenario!).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ryan4yin on GitHub (Dec 1, 2023).
Related to:
@ryan4yin commented on GitHub (Dec 2, 2023):
Secure Boot Enabled: https://github.com/ryan4yin/nix-config/commit/7c61a588086644d77f6aaaa061b61b4488eb4c61
Secure Boot signed all efi images, and it do not store other secrets in /boot, so it's safe to left /boot un-crypted(do not append any secret keys into initrd in this scenario!).