mkinitcpio VS mortar

This file has been changed recently and the wiki still references the old line. You have to modify this line now:

mkinitcpio is an arch thing: https://github.com/archlinux/mkinitcpio

The Arch Linux devs don't have infinite time and energy, so yes less-important issues that affect less users get diprioritized. You're welcome to PR the fix yourself, here's the mkinitcpio repo: https://github.com/archlinux/mkinitcpio

The general logic was changed in the new mkinitcpio release. https://github.com/archlinux/mkinitcpio/pull/54/files

That's an odd one since reinstalling the package fixes the issue. I wouldn't be so sure it's grub because it just loads the vmlinuz and initramfs that are suffixed with the pkgbase. That will not change based on the kernel version and pkgrel version. Someone brought up needing a hook. the mkinitcpio package already installs hooks and scripts necessary for maintaining a mkinitcpio prefix for each kernel for the initramfs image generation and installing vmlinuz to /boot/vmlinuz-${pkgbase} on upgrades. Everyone with the official mkinitcpio package is going to have the same /usr/share/libalpm/scripts/mkinitcpio-install shell script. Running grub-mkconfig is pointless for a kernel upgrade for the reason stated. All it does is export variables from /etc/default/grub and concatenates /etc/grub.d/* into a single config file. If there was a grub config issue it's unlikely you would ever be able to boot.

mkinitcpio made zstd the default on 2021-02-17

The number of thread is, but the compression level isn't. Because -3 is a sane default for the compression level in time of compression time and output file size, but this can differ for your machine. I find that on my machine best compression level is -15 or -16 for size and compression time. Since it will take a 1 second more to compress but it will yield a file 80% more compressed than the default. Here is the pill request where the defaults where changed mkinitcpio#47

Bruteforce of such random password is just not plausible and talks about KDF "weakness" is just a distraction. I think most likely it was evil maid attack.

Here are projects which try to mitigate some of evil maid attack risks:

https://github.com/noahbliss/mortar

https://safeboot.dev/

Secure boot and TPM support (à la Mortar: https://github.com/noahbliss/mortar)

There are tools that look to be able to automate it: https://github.com/noahbliss/mortar/blob/master/docs/proxmox-install.md

I just went through the process of setting up new ubuntu VM's using full root disk LUKS encryption and auto-unlock via Proxmox's vTPM2.0 and UEFI ( via this extremely helpful resource https://github.com/noahbliss/mortar )

I have used this project with Debian+proxmox and it's been working great. https://github.com/noahbliss/mortar but I did read the arch wiki a bit which helped my understanding.

There's a project called "mortar" (as in, gluing all these bricks together) that was attempting to simplify this. Though it's lost steam, reading through it's simple bash scripts was a great place to start for me. This guide for Fedora also helped a lot.

There have been a number of attempts to solve this problem, but the most complete appear to be Mortar (a project I head) and safeboot.dev

I highly recommend taking a look at either of these projects if you want be able to improve both your convenience through auto unlocking, and security through broadened scope of audit.

https://github.com/noahbliss/mortar

https://safeboot.dev

Check out mortar. It uses secure boot and TPM along with LUKS. The creator is super helpful and available on the telegram.

A more advanced approach would be something like mortar to chain-load signed stuff.

There seems to be a workable solution out there for 2.0: https://github.com/noahbliss/mortar/blob/master/docs/proxmox-install.md