void-linux / void-linux/void-docs
FDE guide: Use UUID instead of `/dev/sda*` in crypttab
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 217
- Forks
- 212
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
The FDE guide here currently shows the following example /etc/crypttab:
voidvm /dev/sda1 /boot/volume.key luks
This should be changed to using the UUID of the encrypted device/partition, as the device file names dev/sdx are not deterministic.
Some user on #voidlinux just had an issue where the key file in the initramfs would sometimes not be picked up, and they were asked to enter a passphrase instead. I think this might be because they had /dev/sda1 in their /etc/crypttab like the guide suggests. They reported that using /dev/disk/by-uuid/* worked.
I think dracut also understands some other syntax like UUID=... and even luks-..., but I'm not sure which one is best/correct here. I think the relevant dracut module is /usr/lib/dracut/modules.d/90crypt.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the FDE guide section linked in the issue and inspect its /etc/crypttab example. Check the referenced dracut module at /usr/lib/dracut/modules.d/90crypt to determine the supported UUID syntax, then update the example so it uses a deterministic device identifier and verify the guide's wording is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100