aright, I do think, due to overlays not being...great in vanilla debian, I'll pick up the raspios support and run with it.
now to see if we can bring over cryptsetup-reencrypt
aright, I do think, due to overlays not being...great in vanilla debian, I'll pick up the raspios support and run with it.
now to see if we can bring over cryptsetup-reencrypt
@arrjay what pisses me off about every single distro for the #RaspberryPi is that none of them have #FeatureParity to their #Desktop parts for no good reason.
Something we had on @ubuntu / #Ubuntu 7.04 & @opensuse / #OpenSUSE 10.2 from day 1!
@kkarhan HEE HEE HOO HOO oh boy I have exploded all the installers
but yeah the gearing towards "oh just dump this on an sd card" is not...always helpful
( this current mess of a project is relying on docker to write out a disk image of itself - but at least I know what went in to it better? )
@bls @arrjay I KNOW how to manually encrypt stuff - that's not the point.
It's most likely the reason why @tails_live / @tails / #Tails didn't get a #port to #ARM64 to this day...
AFAIK every #linux for the #raspberrypi comes as a prebuild image for your SD. In my opinion encrypting the filesystem afterwards is the only possible way. Correct me if I'm wrong.
Maybe disc encryption would be a good addition to the first run wizard.
@xeniac I know that this is the case, but it's not a technical unavoidance despite the #RaspberryPi being a non-#UEFI - #arm device.
The solution in that regard would be to boot into a #live / #setup mode like with #RaspberryPiOS for #i586-based #PCs and extend it to a setup that allows creating a new custom image with #LUKS - #FDE enabled and properly encrypted.
I'm not even demanding much, just a simple #TUI / #CLI setup like @ubuntu / #UbuntuServer has with basic customizations.