• 0 Posts
  • 2 Comments
Joined 1 year ago
Cake day: October 20th, 2023
  • MAFoElffen@lemmy.worldtoLinux@lemmy.ml•Warning: ubuntu tpm recovery key cannot unlock disk outside of boot
    1·
    1 year ago

    @Skull giver – I mentioned this above, but couldn’t link it to you.

    I like the code but the go run recover.go 2> key.text does not redirect the key to a file. It does not get input of the recovery key, so errors. Could you please add a few line to write it directly to that file, instead of displaying it? (or both)

    As someone thought, what is displayed onscreen is jibberish, because console cannot display raw hex characters… I’m thinking the LUKS key i the keyslot is raw or hex.

    If I can just find the valid key and write it to a file, then I can help @inchbinjasokreativ to write it to his TPM. I’ve already written a script to do that, but am just missing that key-file. I have the problem replicated o a VM, so can test it on that first.

  • MAFoElffen@lemmy.worldtoLinux@lemmy.ml•Warning: ubuntu tpm recovery key cannot unlock disk outside of boot
    5·
    1 year ago

    As you can see by my UserName, i am the person who filed that Bug as a danger to users…

    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.