Hi everybody, bit of a warning here: The recovery key generated during the installation of Ubuntu 23.10 (if you select tpm-backed fde) cannot be used to unlock the disk outside of boot, as in any ‘cryptsetup’ command and so on will not accept the recovery key. unlocking when accessed from different system does not work etc.
You can use it to unlock the disk while booting if your tpm somehow fails, but ONLY in that specific situation.
I kind of purposefully broke my tpm keys to see if it could be restored with 23.10 and ended up having to reinstal, as I ended up having to enter the recovery key at boot every time and no way of adding additional unlock options to the volume, as cryptsetup would not accept the recovery key as passphrase.
This bug could be very bad for new users.
See this bug report: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2039741
Yet another reason why I wouldn’t put anything important on a tpm encrypted volume 😹 I just don’t trust it
As you can see by my UserName, I am the person who filed that Bug as a danger to users… Specifically brought up by @ichbinsokreativ, me trying to help him…
Thank you Skull giver for the golang code, I had to debug your code, to get it to run, because of the forum transposing HTML char codes for some characters… Unfortunatley, displaying the result onto console displays ‘jibberish’, as you thought might happen. Console cannot display raw hex characters.
Redirecting the output as you posted doesn’t work, as the script then doesn’t get the input of the recovery key, so errors.
I have a request… I know a lot of languages, but GO isn’t one of them. Please… Could you please add a few lines to write the result directly to a file called recovery.key? Then if raw or hex, it would get to a key-file… Then I can test if that is going to work to add additional keys to the LUKS containers, and to be able to help people re-enroll the TPM key.
If you could, they we would have a recovery work-around.
Yes. They did something similar for past ZFS encryptions i their canned installs, but used native ZFS encryption, with a locked encrytped keyfile stored within a LUKS container, that had to be unlocked and mounted before unlocking the ZFS pools. Sometimes I don’t follow the logic behind some things.
It seems like they often add complication to what should be simpler.
Is it still possible to add an extra key (in another slot) to unlock it with cryptsetup? Adding this extra key might beat the purpose of using the TPM but if you choose a long random key and store it in a password manager that should still be pretty safe right?
it’s not, because to to so you need to enter a valid passphrase to cryptsetup, which the recovery key is NOT
Okay so I just read up on this. It’s it true that TPM backed FDE only allows snaps?!?
Debs are completely unsupported?
The ubuntu implementation is based on snap, but if you want to purge snapd (just install another distro at that point though), you can implement encryption as usual and add the tpm later on. Snap is only neccessary if you enable tpm-backed fde from setup.
