Linux

48074 readers

930 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Warning: ubuntu tpm recovery key cannot unlock disk outside of boot (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 1 year ago* (last edited 1 year ago) (1 children)

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.