Update 202610121429 required recovery passphrase

Hi

My server rebooted into 202610121429 this morning, I have TPM encryption enabled but no secure boot.

Server was stuck after reboot, after looking at the console, it was asking for the volume recovery passphrase, after typing it, it seems to boot fine.

Booting on the previous image was asking for the passphrase too.

I’m not sure if it’s worth a github issue?

I’ll look into it.

Once successfully booted on the new image, can you run incus admin os system security tpm-rebind? That will reboot the system and hopefully no longer prompt for the recovery key.

@gibmat looks like the new systemd has changed how systemd-stub measures things in a non-secureboot environment… Kinda annoying as it means it’s not something that we can fix in a new image…

Anyone currently running with SecureBoot disabled will need to enter the recovery key and do a TPM rebind. Thankfully the no-SecureBoot but physical TPM is by far the least common setup, but it’s still pretty annoying when we don’t have a way to prevent it…

I’m preparing a change to incus-osd to harden against future similar changes by systemd.

It works fine, thanks!