A request to use luks2 when installing solus with encryption

ChaoticChrono

I just have a tiny gripe each time I install solus on my pc and that is each time I install it I need to switch to luks2 so that I can use tpm to unlock my disks, Now I get it luks1 was required to boot when grub was used with full disk encryption but with systemd-boot it just doesn't make sense to not use luks2 by default unless there is some sort of technical issue I am unaware of

alfisya

We are working on it. With the updated calamares, it is very possible this can happen in the next ISO release (No promises, No ETA).

If you want to get early access to our ISO, you can support us at Open Collective.

Cheers!

Clintre

Yep as alfisya said we are on it. It was one of the early things when I first started using Soluse that I mentioned as well. The blocker was the older version of grub and issues around it.

Meanwhile, there are a few ways to work around it during install on the current 4.8 ISO IF you are on a system with UEFI. If you are on an older system with legacy bios this will cause problems. I know you mentioned systemd-boot, but in case anyone else stumbles across this.

When you boot into the ISO for the install...

Do not launch the Installer / Calamares
Open terminal and nano /usr/sharecalamares/modules/parition.conf
Above defaultFileSystemType add luksGeneration: "luks2"
Save, close, and launch the Installer

It seems you already know how to do it, but I also have a guide on switching post install...
https://discuss.getsol.us/d/11788-luks2-tpm-auto-unlock-for-already-installed-solus-guide

ChaoticChrono

alfisya
Alright man this was just a little gripe of mine
would love to support ya'll but currently am a uni student so in a budget crunch 😅

Xoph

ChaoticChrono Been there!! LOL