From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox/installer/docs 0/8] installer: add full-disk encryption of the system disks
Date: Wed, 18 Nov 2026 00:42:23 +0100 [thread overview]
Message-ID: <20261117234330.801935-1-t.lamprecht@proxmox.com> (raw)
This series lets the installer encrypt the system disks with a
passphrase that has to be entered at every boot, so that the data of a
powered-off or removed server cannot be read. It covers all products,
the graphical and the terminal installer, and answer files.
ext4 and xfs installations put the LVM volume group into a LUKS2
container, Btrfs installations get one container per disk, and ZFS
installations use native ZFS encryption with the pool as encryption
root. All of them boot through proxmox-boot-tool, and the stock
initramfs asks for the passphrase. The option is only offered if the
installer was booted in UEFI mode.
ZFS uses its native encryption rather than a LUKS2 container under
every disk, so that data is encrypted once instead of once per mirror
or RAIDZ member, and replacing a disk works as without encryption. In
return, dataset names, properties and space usage stay readable, and
the key is derived with PBKDF2 instead of Argon2id. The second docs
patch drops the experimental label from native ZFS encryption, as the
issues it cited are fixed.
ZFS installations get a single passphrase for now, as native encryption
has one key per encryption root. A recovery passphrase or TPM2 and
FIDO2 unlocking can come later without a reinstall: `zfs change-key`
can switch an installed pool in place to a random key kept in a small
LUKS2 key store, whose key slots then provide them.
In the mid/long term I'd also like to add support to setup unlocking
with a TPM or FIDO2 token directly here, and likely also allowing UKIs
for a full measured boot [0]. But this is not supported yet, as among
other things Debian's initramfs-tools cannot use such key slots at boot,
so we'd need to switch to dracut and also need to sign systemd-boot.
For now the docs describe adding a recovery passphrase and unlocking
over SSH after the installation.
[0]: https://0pointer.de/blog/brave-new-trusted-boot-world.html
The installer patches need a proxmox-installer-types release with the
proxmox patch, and the ISO needs cryptsetup and cryptsetup-initramfs
in its package pool, plus keyutils for PDM. PDM gets its own patch on
pdm-devel.
I tested all four products in VMs: every file system, single and
multi-disk, with and without Secure Boot, interactive and automated,
including a non-ASCII passphrase with a German keyboard layout,
reinstalling over an existing LUKS container and the rescue procedure
from the docs.
Sending them mostly to give them some early exposure, while this
MVP is rather polished, there is no need to rush this.
proxmox:
Thomas Lamprecht (1):
installer-types: add full-disk encryption to the disk setup
proxmox-installer-types/src/answer.rs | 141 ++++++++++++++++++++++-
proxmox-installer-types/src/lib.rs | 22 ++++
proxmox-installer-types/src/post_hook.rs | 5 +-
3 files changed, 165 insertions(+), 3 deletions(-)
installer:
Thomas Lamprecht (5):
install: encrypt the system disks with LUKS2 or native ZFS encryption
auto: support full-disk encryption in answer files
chroot enter: unlock the LUKS containers of an encrypted installation
ui: offer full-disk encryption in the graphical and terminal installer
assistant: keep the disk passphrase out of prepared ISOs
Cargo.toml | 2 +-
Proxmox/Install.pm | 254 ++++++++++++-
Proxmox/Install/Config.pm | 15 +
Proxmox/Sys/Block.pm | 2 +-
debian/control | 3 +-
html/ack_template.htm | 2 +
html/pbs/passwd.htm | 1 +
html/pdm/passwd.htm | 1 +
html/pmg/passwd.htm | 1 +
html/pve/passwd.htm | 1 +
proxinstall | 99 ++++-
proxmox-auto-install-assistant/src/main.rs | 93 ++++-
proxmox-auto-installer/src/utils.rs | 13 +-
proxmox-auto-installer/tests/parse-answer.rs | 5 +
.../parse_answer/encryption_luks.json | 26 ++
.../parse_answer/encryption_luks.toml | 17 +
.../parse_answer/encryption_zfs.json | 36 ++
.../parse_answer/encryption_zfs.toml | 24 ++
.../encryption_empty_passphrase.json | 3 +
.../encryption_empty_passphrase.toml | 17 +
.../encryption_passphrase_control_char.json | 3 +
.../encryption_passphrase_control_char.toml | 17 +
.../encryption_passphrase_too_short.json | 3 +
.../encryption_passphrase_too_short.toml | 17 +
proxmox-chroot/src/main.rs | 351 ++++++++++++++++--
proxmox-installer-common/src/options.rs | 3 +
proxmox-installer-common/src/setup.rs | 17 +
proxmox-post-hook/src/main.rs | 8 +-
proxmox-tui-installer/src/main.rs | 68 +++-
proxmox-tui-installer/src/options.rs | 19 +-
proxmox-tui-installer/src/setup.rs | 9 +-
proxmox-tui-installer/src/views/bootdisk.rs | 49 ++-
proxmox-tui-installer/src/views/mod.rs | 6 +
test/Makefile | 7 +-
test/fde-preflight.pl | 143 +++++++
35 files changed, 1257 insertions(+), 78 deletions(-)
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/encryption_luks.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/encryption_luks.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/encryption_zfs.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/encryption_zfs.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/encryption_empty_passphrase.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/encryption_empty_passphrase.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/encryption_passphrase_control_char.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/encryption_passphrase_control_char.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/encryption_passphrase_too_short.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/encryption_passphrase_too_short.toml
create mode 100755 test/fde-preflight.pl
docs:
Thomas Lamprecht (2):
installation: describe full-disk encryption
local-zfs: update the limitations of native encryption
local-zfs.adoc | 23 +++--
pve-installation.adoc | 222 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 233 insertions(+), 12 deletions(-)
--
2.47.3
next reply other threads:[~2026-11-17 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 23:42 Thomas Lamprecht [this message]
2026-11-17 23:42 ` [PATCH proxmox 1/1] installer-types: add full-disk encryption to the disk setup Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 1/5] install: encrypt the system disks with LUKS2 or native ZFS encryption Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 2/5] auto: support full-disk encryption in answer files Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 3/5] chroot enter: unlock the LUKS containers of an encrypted installation Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 4/5] ui: offer full-disk encryption in the graphical and terminal installer Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 5/5] assistant: keep the disk passphrase out of prepared ISOs Thomas Lamprecht
2026-11-17 23:42 ` [PATCH docs 1/2] installation: describe full-disk encryption Thomas Lamprecht
2026-11-17 23:42 ` [PATCH docs 2/2] local-zfs: update the limitations of native encryption Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261117234330.801935-1-t.lamprecht@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.