02-24-2020, 09:22 AM
(02-24-2020, 08:38 AM)FeMike Wrote:(02-24-2020, 08:14 AM)danielt Wrote: No worries.I was just getting ready to ask about that. I thought encryption wasn't supported by default kernel. If I wanted encryption I would have to install first then rerun script with new kernel to get it. Or are those two different things? Getting back to setting up with encryption you're saying that just by calling that variable CRYPT will encrypt it even with saying CRYPT=n?
BTW I think I noticed something about CRYPT=n in some of the other posts. The code to handle variables is a but crude and 'y' is just a mnemonic: you can set it to anything you like and it will enable encryption... if you don't want encryption then don't set it to anything.
Pretty much, yes. The test used is "is CRYPT not empty" rather than "is CRYPT equal to y" (and CRYPT is empty by default). I'm not saying that is the *best* thing... but currently that is what is does.
Regarding the "install first and then re-run" business, it is true encryption wasn't support by the default kernel... but I think that has changed recently. Certainly the fact you got to a bootable SD card (even without a GUI) suggest a direct encrypted install is now possible.