-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
systemd: Fix systemd-{cryptenroll,cryptsetup} TPM2 and FIDO2 support (attempt #3) #189676
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
f42cdfe
cryptsetup: Allow reading tokens from relative path
zhaofengli 570824e
systemd: Wrap in LUKS2 tokens
zhaofengli 19c34ac
systemd/initrd: Add files required by TPM2 and FIDO2 support to the i…
zhaofengli 9e9637e
nixos/tests/systemd-initrd-luks-tpm2: init
JJJollyjim 21bbef9
nixos/luksroot: Reword message on FIDO2 support with systemd stage 1
zhaofengli b9b4548
systemd/initrd: Add TPM modules into initrd
zhaofengli 78f929c
nixos/tests/systemd-initrd-luks-fido2: init
oxalica File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| import ./make-test-python.nix ({ lib, pkgs, ... }: { | ||
| name = "systemd-initrd-luks-fido2"; | ||
|
|
||
| nodes.machine = { pkgs, config, ... }: { | ||
| # Use systemd-boot | ||
| virtualisation = { | ||
| emptyDiskImages = [ 512 ]; | ||
| useBootLoader = true; | ||
| useEFIBoot = true; | ||
| qemu.package = lib.mkForce (pkgs.qemu_test.override { canokeySupport = true; }); | ||
| qemu.options = [ "-device canokey,file=/tmp/canokey-file" ]; | ||
| }; | ||
| boot.loader.systemd-boot.enable = true; | ||
|
|
||
| boot.initrd.systemd.enable = true; | ||
|
|
||
| environment.systemPackages = with pkgs; [ cryptsetup ]; | ||
|
|
||
| specialisation.boot-luks.configuration = { | ||
| boot.initrd.luks.devices = lib.mkVMOverride { | ||
| cryptroot = { | ||
| device = "/dev/vdc"; | ||
| crypttabExtraOpts = [ "fido2-device=auto" ]; | ||
| }; | ||
| }; | ||
| virtualisation.bootDevice = "/dev/mapper/cryptroot"; | ||
| }; | ||
| }; | ||
|
|
||
| testScript = '' | ||
| # Create encrypted volume | ||
| machine.wait_for_unit("multi-user.target") | ||
| machine.succeed("echo -n supersecret | cryptsetup luksFormat -q --iter-time=1 /dev/vdc -") | ||
| machine.succeed("PASSWORD=supersecret SYSTEMD_LOG_LEVEL=debug systemd-cryptenroll --fido2-device=auto /dev/vdc |& systemd-cat") | ||
|
|
||
| # Boot from the encrypted disk | ||
| machine.succeed("bootctl set-default nixos-generation-1-specialisation-boot-luks.conf") | ||
| machine.succeed("sync") | ||
| machine.crash() | ||
|
|
||
| # Boot and decrypt the disk | ||
| machine.wait_for_unit("multi-user.target") | ||
| assert "/dev/mapper/cryptroot on / type ext4" in machine.succeed("mount") | ||
| ''; | ||
| }) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| import ./make-test-python.nix ({ lib, pkgs, ... }: { | ||
| name = "systemd-initrd-luks-tpm2"; | ||
|
|
||
| nodes.machine = { pkgs, ... }: { | ||
| # Use systemd-boot | ||
| virtualisation = { | ||
| emptyDiskImages = [ 512 ]; | ||
| useBootLoader = true; | ||
| useEFIBoot = true; | ||
| qemu.options = ["-chardev socket,id=chrtpm,path=/tmp/mytpm1/swtpm-sock -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0"]; | ||
| }; | ||
| boot.loader.systemd-boot.enable = true; | ||
|
|
||
| boot.initrd.availableKernelModules = [ "tpm_tis" ]; | ||
|
|
||
| environment.systemPackages = with pkgs; [ cryptsetup ]; | ||
| boot.initrd.systemd = { | ||
| enable = true; | ||
| }; | ||
|
|
||
| specialisation.boot-luks.configuration = { | ||
| boot.initrd.luks.devices = lib.mkVMOverride { | ||
| cryptroot = { | ||
| device = "/dev/vdc"; | ||
| crypttabExtraOpts = [ "tpm2-device=auto" ]; | ||
| }; | ||
| }; | ||
| virtualisation.bootDevice = "/dev/mapper/cryptroot"; | ||
| }; | ||
| }; | ||
|
|
||
| testScript = '' | ||
| import subprocess | ||
| import os | ||
| import time | ||
|
|
||
|
|
||
| class Tpm: | ||
| def __init__(self): | ||
| os.mkdir("/tmp/mytpm1") | ||
| self.start() | ||
|
|
||
| def start(self): | ||
| self.proc = subprocess.Popen(["${pkgs.swtpm}/bin/swtpm", "socket", "--tpmstate", "dir=/tmp/mytpm1", "--ctrl", "type=unixio,path=/tmp/mytpm1/swtpm-sock", "--log", "level=20", "--tpm2"]) | ||
|
|
||
| def wait_for_death_then_restart(self): | ||
| while self.proc.poll() is None: | ||
| print("waiting for tpm to die") | ||
| time.sleep(1) | ||
| assert self.proc.returncode == 0 | ||
| self.start() | ||
|
|
||
| tpm = Tpm() | ||
|
|
||
|
|
||
| # Create encrypted volume | ||
| machine.wait_for_unit("multi-user.target") | ||
| machine.succeed("echo -n supersecret | cryptsetup luksFormat -q --iter-time=1 /dev/vdc -") | ||
| machine.succeed("PASSWORD=supersecret SYSTEMD_LOG_LEVEL=debug systemd-cryptenroll --tpm2-pcrs= --tpm2-device=auto /dev/vdc |& systemd-cat") | ||
|
|
||
| # Boot from the encrypted disk | ||
| machine.succeed("bootctl set-default nixos-generation-1-specialisation-boot-luks.conf") | ||
| machine.succeed("sync") | ||
| machine.crash() | ||
|
|
||
| tpm.wait_for_death_then_restart() | ||
|
|
||
| # Boot and decrypt the disk | ||
| machine.wait_for_unit("multi-user.target") | ||
| assert "/dev/mapper/cryptroot on / type ext4" in machine.succeed("mount") | ||
| ''; | ||
| }) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50 changes: 50 additions & 0 deletions
50
pkgs/os-specific/linux/cryptsetup/relative-token-path.patch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| From 4f95ab1f8110a8ab9d7b0e192731ce467f6e5c26 Mon Sep 17 00:00:00 2001 | ||
| From: =?UTF-8?q?Janne=20He=C3=9F?= <janne@hess.ooo> | ||
| Date: Sun, 4 Sep 2022 11:15:02 -0600 | ||
| Subject: [PATCH] Allow loading token handlers from the default search path | ||
|
|
||
| Since [1] landed in cryptsetup, token handlers (libcryptsetup-token-*.so) | ||
| are loaded from a fixed path defined at compile-time. This is | ||
| problematic with NixOS since it introduces a dependency cycle | ||
| between cryptsetup and systemd. | ||
|
|
||
| This downstream patch [2] allows loading token plugins from the | ||
| default library search path. This approach is not accepted upstream [3] | ||
| due to security concerns, but the potential attack vectors require | ||
| root access and they are sufficiently addressed: | ||
|
|
||
| * cryptsetup could be used as a setuid binary (not used in NixOS). | ||
| In this case, LD_LIBRARY_PATH is ignored because of secure-execution | ||
| mode. | ||
| * cryptsetup running as root could lead to a malicious token handler | ||
| being loaded through LD_LIBRARY_PATH. However, fixing the path | ||
| doesn't prevent the same malicious .so being loaded through LD_PRELOAD. | ||
|
|
||
| [1] https://gitlab.com/cryptsetup/cryptsetup/-/commit/5b9e98f94178d3cd179d9f6e2a0a68c7d9eb6507 | ||
| [2] https://github.com/NixOS/nixpkgs/issues/167994#issuecomment-1094249369 | ||
| [3] https://gitlab.com/cryptsetup/cryptsetup/-/issues/733 | ||
| --- | ||
| lib/luks2/luks2_token.c | 4 +--- | ||
| 1 file changed, 1 insertion(+), 3 deletions(-) | ||
|
|
||
| diff --git a/lib/luks2/luks2_token.c b/lib/luks2/luks2_token.c | ||
zhaofengli marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| index 26467253..6f8329f0 100644 | ||
| --- a/lib/luks2/luks2_token.c | ||
| +++ b/lib/luks2/luks2_token.c | ||
| @@ -151,12 +151,10 @@ crypt_token_load_external(struct crypt_device *cd, const char *name, struct cryp | ||
|
|
||
| token = &ret->u.v2; | ||
|
|
||
| - r = snprintf(buf, sizeof(buf), "%s/libcryptsetup-token-%s.so", crypt_token_external_path(), name); | ||
| + r = snprintf(buf, sizeof(buf), "libcryptsetup-token-%s.so", name); | ||
| if (r < 0 || (size_t)r >= sizeof(buf)) | ||
| return -EINVAL; | ||
|
|
||
| - assert(*buf == '/'); | ||
| - | ||
| log_dbg(cd, "Trying to load %s.", buf); | ||
|
|
||
| h = dlopen(buf, RTLD_LAZY); | ||
| -- | ||
| 2.37.2 | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we maybe make this optional? Or conditional on if the kernel has this option set?
I have some custom kernel configs that really don't need this module and also use the new initrd and now the initrd build fails with
modprobe: FATAL: Module tpm-tis not found in directory […].There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we can have a new option under
boot.initrd.luks.devices.<name>that indicates whether a LUKS makes use of cryptenroll-based TPM2/FIDO2 unlocking, and only insert the modules and extra files when a volume with those options enabled exists. However, this can be confusing for non-systemd-stage1 users, especially whenboot.initrd.luks.devices.<name>.fido2already exists.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer if disabling these kernel modules would an opt-in config option.
We can't determine at evaluation time if there's a fido luks slot configured.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fair enough. iirc we can determine at eval time if the kernel even has these modules enabled. maybe using
system.requiredKernelConfig?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking at the kernel config, these options/modules don't even seem to be available on non-x86 systems or systems without ACPI, so I'm really not sure they should be enabled by default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmh, that'd be a problem. Can we check if the kernel has these modules configured, and only include them in that case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think something like this might work:
but only if we actually set these options and don't rely on kernel defaults. Maybe.
For some reason
nixosTests.systemd-initrd-luks-fido2andnixosTests.systemd-initrd-luks-tpm2build even with:so I'm not sure how to test.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The VM test passes without adding any extra modules but on (some?) actual hardware they are required.