Actually the issue arise only if you switch from argon2i to argon2id (this is what means the header conversion). In any case for such a transition I would first decrypt the drive
then re-encrypt it with another algorithm (and in Slint there is no separate /boot partition anyway).

So this is only an issue upon conversion, but not from creating an encrypted volume from scratch?
I don't quite understand.
Right now I'm using LUKS1

My understanding is that that whatever you do GRUB is not yet able to support argon2id according to Matthew.This is also what is used by the Slint installer if encryption is requested. I have considered switching to Argon2 for the incoming new version of the installer, but the drawback is that could require a lot of RAM depending on the settings, beyond the current requirement to install Slint which is at least 2G, if I understand the part 4 Parameter Choice of the RFC 9106.

1 members found this post helpful.

Is there somewhere I could get closer information on this?
I'd really prefer FDE and have already set up my machines this way but would still like to have the newer much more secure standards.

Eventually it is unclear to me whether argon 2id is already supported by GRUB or not. Best would be to ask the devs:
https://lists.gnu.org/mailman/listinfo/grub-devel/

Sorry to resurrect a year old thread, but I went down this same road last week and this post was extremely helpful. I have full disk encryption on my laptop as was getting tired of having to type my password three times (power on, unlock root, unlock swap). After playing around in a VM I first realized I could set my swap up in a different way so that I would not need a password. I then weighed my options for a one password option for power on and root, first I thought about using the TPM, but abandoned that almost immediately. I then decided to use a key embedded in the initramfs. This could be accomplished using dracut, but I found a guide that allowed me to do it in stock slackware without any third party packages. All that is really needed is a small tweak to the initrd init.

https://yellowapple.us/2022/02/10/sl...-efi-only.html

This guide assumes you are going to setup your drive in a LVM configuration. If you want to do that you can follow the guide almost exactly, but you don't have to. I tested it in a VM and you can setup your drive in a normal configuration and it will still work, you'll just have to make a few modifications.

1 members found this post helpful.

I have done something like that patching mkinitrd: https://www.linuxquestions.org/quest...5/#post6301332
I also requested to apply this patch in the genuine mkinitrd: https://www.linuxquestions.org/quest...5/#post6301332 to no avail. However as switching to dracut made my life of package/distribution maintainer way easier I don't care.

1 members found this post helpful.

I tried dracut and found it pretty interesting, but I admittedly didn't get very far with it. I am thinking about RTFM and playing around with it in a VM.