Hi folks,
I have Alpine Linux installed in an encrypted LUKS partition. I came across this tutorial which shows how to setup a key in a USB drive and when the drive is inserted and the computer booted, the LUKS partition auto-unlocks with the key on the USB drive.
I would like to setup the same thing but I do not have Alpine linux installed on ZFS, so I'm looking for ways to adapt the instructions.
So far, what I've done is:
- I've setup the key on the usb stick and I can unlock the LUKS partition with that key.
- create a
/etc/mkinitfs/features.d/usb-unlock.shscript with the following content:
(the echo to /dev/kmesg was to check whether the script did indeed run at boot by trying to print to the kernel messages but I can't find anything in the kernel messages).
#!/bin/sh
echo "usb-unlock script starting..." > /dev/kmsg
USB_MOUNT="/mnt/my-usb-key" # The USB stick mounting point
LUKS_KEY_FILE="awesome.key" # The name of your keyfile on the USB stick
# Search for the USB stick with the key
for device in $(ls /dev/disk/by-uuid/*); do
mount $device $USB_MOUNT 2>/dev/null
if [ -f "$USB_MOUNT/$LUKS_KEY_FILE" ]; then
# Unlock the LUKS partition
cryptsetup luksOpen /dev/sda3 cryptroot \
--key-file "$USB_MOUNT/$LUKS_KEY_FILE" && exit 0
fi
umount $USB_MOUNT
done
echo "No USB key found, falling back to password prompt." # this message never appears, despite not having found the key on the usb stick
echo "usb-unlock script ending." > /dev/kmsg
- I added
usb-unlockto thefeaturesinmkinitfs.conf:
mytestalpine:~# cat /etc/mkinitfs/mkinitfs.conf
features="ata base ide scsi usb virtio ext4 cryptsetup keymap usb-unlock"
- run
mkinitfsto rebuild the initramfs. Then reboot to test the implementation, which was unsuccessful.
What am I missing / doing wrong? Thank you for your help!
Edit: forgot to add step 4
I'm very grateful for your extended help. I've made some progress. I'm able to get the prompt to appear asking me for my passphrase to unlock the right partition (sda3 in my case). Entering the passphrase, however, drops me in the Dracut emergency shell after ~3min of dracut logs, seemingly looping. (Edit: the reason for why it drops me in the shell is very unclear. It says
Dropping to debug shell. /bin/sh: can't access tty: job control turned off.And if I try to exit the dracut shell, it saysdracut Warning: could not boot.).In the Dracut emergency shell, checking
/dev/mapper/I see aluks-<sda3-uuid>listed. RunningblkidI see it listed too withTYPE=crypto_LUKS. I also see adev/dm-0with a dedicated UUID, in ext4. I ranblkidwhich shows:I checked the status of the filesystem running
cryptsetup status /dev/mapper/luks-<sda3-uuid>and it says itis active, which I guess means it is unlocked?I checked the
/rootdirectory, and it is empty. So I tried to mount the partition myself:mount /dev/mapper/luks-<sda3-uuid> /rootbut it fails sayingmount: mounting /dev/mapper/luks-<sda3-uuid> on /root failed: No such file or directoryand that got me really puzzled? I've been searching far and wide but I can't seem to find anyone with a similar situation. I feel like I'm close to getting this working.Below is my syslinux kernel config, and the 2nd and 3rd items are what I booted into (
/boot/extlinux.conf)And here the
/proc/cmdlineof the booted partition:Here is my setup, when I boot in my regular initramfs (the one I'm trying to replicate using dracut):
Note: No idea of the relevance, but I'm testing this setup in a VM, with a BIOS firmware.
Sorry, I've had a (self-imposed) busy week, but I have to admit, that also has me rather stumped. As far as I can tell, your second entry should work. If the device is visible in /dev/mapper under a name, it should be able to mount under that name.
The only thing I can think of is that some important module like the ext4 module might be missing somehow? You can get pretty confusing errors when that happens. Dracut is supposed to parse
/etc/fstabfor everything needed to boot, and maybe that's not recognizing your root for some reason.dmesgmight have some useful info at the end after you try to mount it. If that's what's happening, you could try to addadd_drivers+=" ext4 "in your dracut.conf and regenerate it (the spaces are important!). But if that's not it, then I'm probably out of ideas now.