cryptsetup: add support for unlocking cryptsetup volumes via FIDO2 + TPM2 + add systemd-cryptenroll tool + more - #17741
Conversation
|
This is based on top of #17524 btw, and includes its commits as long as that one is not merged. |
1b3589c to
026ff13
Compare
db5b235 to
f1f096d
Compare
704624f to
03de19f
Compare
e3ab11b to
deac4a4
Compare
982b82a to
41b99bd
Compare
46e8937 to
a7e6c36
Compare
|
#17884 should get merged soon, once that happens please rebase and add libfido2 to the test as well |
That way we can reuse it from systemd-cryptenroll
That way we can use it later on in systemd-cryptsetup to unlock devices with FIDO2 tokens.
Apparently devices are supposed to generate failures if we try to turn off features they don't have. Thus don't. Prompted-by: systemd#17784 (comment)
…KCS#11 security tokens
This is similar to the base64 support, but fixed-size hash values are typically preferably presented as series of hex values, hence store them here like that too.
This useful for bootstrapping encrypted systems: on first boot let's create a /var/ partition that is locked to the local TPM2.
6397228 to
80670e7
Compare
|
New version posted with the debian/ubuntu mkosi file updated as suggested. no other changes. let's see if this works this time |
|
I've also tested this on Archlinux to unlock my These dependencies can't be automatically discovered (for now), since systemd-cryptsetup is using ¹ I'm using the AMD fTPM (on a Ryzen 5 3600 cpu and MSI B550m motherboard). |
|
@gdamjan Basically I ran Do you happen to know what modifications are needed in the initramfs config for FIDO2 tokens? |
|
@L0g4n let's take this to the Arch forum or to the systemd irc |
This adds five things:
pkcs11-uri=autoto the crypttab options of the device. (Similar logic is also done for FIDO2 support, making it equallty easy to use).