ok lets get this in order
i update alpine, normal stuff for me i always pick the weirdest times for updates
i hibernate 5 minutes later
that was timed at right the damn moment the bootloader was being regenerated
that fucks up the bootloader
i cannot boot, it cannot find the disk, the initramfs image is incapable of seeing thin circular data storage medium devices, ok after hopelessly trying to recover it from within itself i give up and decide to try again with a real recovery environment
i fight the alpine installer for a moment, i manage to unhibernate it in a broken sort of way after finishing(?) the update, but in reality it does not make much more progress boot wise (read only isnt even helpful in recovery how tf do you recover a read only fs)
i regenerate the entire damn bootloader, kernel image, initramfs, extlinux, THE BOOT ENTRY FROM THE STUPID TABLE DISAPPEARS what the fuck 

hey @kzimmermann hardware scheduled maintenance for me so ill be reinstalling with UEFI and i hope disk encryption sooner rather than later, tried pestering a friend about it but decided its not worth it, i believe you use full disk encryption, do you have some recommendations for casual full disk encryption?

i do not need deniable encryption, i think i can manage to memorize a passphrase with sufficient entropy, not particularily worried i would forget it (if i did then it wasnt important after all, and i would rather depend on remembering it than on a device that can be stolen or lost), i can figure out the algos to pick (argon2id if its available and likely some chacha)

@sylvie hey there! For #AlpineLinux, I just go with the standard LUKS full disk encryption that's offered by the installer script. Nothing fancy, just something that's simple and fast to set up, costs me nothing and works for me.

But to be frank: I have no idea about the algorithm it uses or anything else under the hood. Surely it can be tweaked, even at the script's level, but if you need to set up something more specific to your use case, I'm afraid I can't help. But have a boost; hopefully somebody more well versed in FDE can help!

@kzimmermann ok so you can check with

# cryptsetup luksDump /dev/your_encrypted_partition_eg_sda2

the default seems to be argon2id and aes-xts-plain64, i would have preferred chacha of some kind but that seems to require figuring out how to, well, get the appropriate module for that

so now i just need to figure out how to load a VESA driver into the initramfs and make it display some silly splash screen while it asks for the decryption key

restoring my backup (all 4 gigabytes compressed down to just 2 and i used lzop which doesnt have entropy coding so im really curious where it found 2 gigabytes of redundancy in that) will have to come at a later date