Encrypted root partition
by resolver from LinuxQuestions.org on (#55DYT)
Hi all,
I have a fast(ish) SSD that I want to use as my encrypted root partition, and then I'd use an old 1GB microSD as the boot device for my Raspberry Pi 4b 8GB.
I didn't see anything on the Sarpi.fatdog.eu webpage though about how to set up a LUKS encrypted root partition. I've done it on a regular PC a few times but that's a whole different ballgame.
For Slackware 32-bit on a Pi, he requires deleting the initrd tarball, whereas on a regular PC I'd mkinitrd.
He provides a blob called bootcode.bin and 196 device tree files (extension .dtbo).
He provides a number of "fixup" .dat files.
So I'm wondering if there is something profoundly different about booting on a Raspberry Pi that will prevent an encrypted root.
Has anyone here succeeded at doing this already?
BTW I have managed in the recent past to boot a Pi with Slackware 32-bit and the kernel prompts me for the password to unlock a non-root partition.
Thanks.
I have a fast(ish) SSD that I want to use as my encrypted root partition, and then I'd use an old 1GB microSD as the boot device for my Raspberry Pi 4b 8GB.
I didn't see anything on the Sarpi.fatdog.eu webpage though about how to set up a LUKS encrypted root partition. I've done it on a regular PC a few times but that's a whole different ballgame.
For Slackware 32-bit on a Pi, he requires deleting the initrd tarball, whereas on a regular PC I'd mkinitrd.
He provides a blob called bootcode.bin and 196 device tree files (extension .dtbo).
He provides a number of "fixup" .dat files.
So I'm wondering if there is something profoundly different about booting on a Raspberry Pi that will prevent an encrypted root.
Has anyone here succeeded at doing this already?
BTW I have managed in the recent past to boot a Pi with Slackware 32-bit and the kernel prompts me for the password to unlock a non-root partition.
Thanks.