Switch from busybox to systemd initramfs hooks#4237
Closed
h8d13 wants to merge 1 commit intoarchlinux:masterfrom
Closed
Switch from busybox to systemd initramfs hooks#4237h8d13 wants to merge 1 commit intoarchlinux:masterfrom
busybox to systemd initramfs hooks#4237h8d13 wants to merge 1 commit intoarchlinux:masterfrom
Conversation
- Always use sd-encrypt instead of encrypt (kept libfido2 for HSM) - Use rd.luks.name= kernel params instead of cryptdevice= - Remove mkinitcpio busybox fallback (systemd->udev, sd-vconsole->keymap)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently if a user doesn't setup HSM/FIDO2 (which most don't) he will take the path of
busybox, here we change all of them tosystemdinit hooks. This was even commented in codeAnd requested: #3989 about a year ago (and a bit of a can of worms since historically is an interesting subject #102 #861)
This would also allow for auto-unlocks using
/etc/cryptsetup-keys.d/viaFILES=hook andGRUB2that supports unlocking non-UKI when/bootis on encrypted parts with single prompt (pbkdfand newargon2id)On top of that it makes it simpler for user to setup desired
TPM2orFIDO2and/orsbctlsystemd-cryptenrollpost-install, which often requires some involved "setup" steps or hw compatibility check which (is hard to do in fullyautomated flow in the first place.)
Most lamda users probably don't have
U2Fkeys. I haven't tested that in a bit...Branch tested
LUKS2and non encrypted which seem to work fine, and will be testingLVMcasesTLDR; Basically the
busyboxhooks workarounds feels awkwardly hacky and is given as a default to most users, which then they have to "fix" for their desired more "advanced" features (or for the more modern standard/counterpart) https://wiki.archlinux.org/title/Mkinitcpio#Hook_list