• lengau@midwest.social
      link
      fedilink
      arrow-up
      7
      ·
      9 months ago

      There are plenty of ways to do TPM backed FDE on earlier Ubuntu. They’re just not officially supported. Clevis is one of the easier ways.

    • kn33@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 months ago

      The disk will be decrypted on boot, but then they’ll have to contend with needing a password to log in

      • catloaf@lemm.ee
        link
        fedilink
        English
        arrow-up
        7
        ·
        9 months ago

        Unless recovery (single user) mode is enabled. If it is, you can boot right into a root shell from the bootloader.

    • asudox@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Guess I’ll wait for COSMIC DE’s alpha release then. It should come with Pop!_OS 24.04

    • asudox@lemmy.worldOP
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      edit-2
      9 months ago

      TPM isn’t an encryption algorithm. TPM just holds the decryption key (in my case the LUKS decryption key) and hands it to the CPU if all checks pass for convenience. No key is stored in the storage in plaintext. TPM isn’t the most secure thing but at least its better than nothing at all.

      • vexikron@lemmy.zip
        link
        fedilink
        arrow-up
        3
        arrow-down
        8
        ·
        9 months ago

        Sure but you dont need to use TPM at all to use LUKS.

        You can store the encryption key on the harddrive, in the LUKS partition layer.

        Like thats the default of how LUKS works.

        Im really confused why people think TPM needs to be involved in anyway when using LUKS.

        Generally speaking you have to go out of your way to correctly cajole TPM v1 or v2 to actually correctly interface with LUKS.

        • GreyBeard@lemmy.one
          link
          fedilink
          arrow-up
          8
          ·
          9 months ago

          The point is to have the system automatically unlock without the need for a boot password. This provides decent security if secure boot is enabled, but requires very little from the user. It isn’t a stopper for high threats, but a simple theft will mean the data is safe. It also ensures that if the drive is separated from the host machine, it is useless without a copy of they key. It doesn’t stop all threats, but stops a lot of them, and all of the most common.

          • vexikron@lemmy.zip
            link
            fedilink
            arrow-up
            1
            arrow-down
            9
            ·
            9 months ago

            Oh ok so the use case here is if this casual linux user asking this question has only their harddrive stolen from their pc or their laptop in their home or apartment or workplace, not their whole pc.

            Mhm that seems likely.

            I guess this maybe makes sense if youre running like a server room, but chances are low thats the actual context of this question.

            Why would you run PopOS on a large operation’s servers?

            • ShortN0te@lemmy.ml
              link
              fedilink
              arrow-up
              7
              ·
              9 months ago

              While i am personally also not a huge fan of TPM for FDE it is still a valid use. Why? In order to access data on the disk you would still need to bypass the login screen which is non trivial. Also another use case is encrypting the drive so when you sell it or dispose of it you do not need to worry about wiping it at least once to get rid of all data.

              TPM has its weaknesses but pls don’t talk down to someone who wants to use it when you do not understand his use case.

              • GreyBeard@lemmy.one
                link
                fedilink
                arrow-up
                3
                ·
                edit-2
                9 months ago

                It should stop issues with full device theft as well, if done correctly, because if secure boot isn’t on and working, it will refuse to give the key. Which means, if it was setup correctly, the computer cannot be accessed without know the users name and password. This is the general accepted stack for Microsoft’s BitLocker. It becomes completely transparent to the user, but puts a decent blocker to access in cases of theft. There are ways around it like freezing RAM or packet sniffing an external TPM, but those are high level attacks.

        • kn33@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          9 months ago

          Im really confused why people think TPM needs to be involved in anyway when using LUKS.

          Because it’s convenient

          • vexikron@lemmy.zip
            link
            fedilink
            arrow-up
            1
            arrow-down
            6
            ·
            9 months ago

            Its not though, it requires a ton of extra work to set up, isn’t necessary, doesn’t allow you to do anything you can’t do without it.

            • kn33@lemmy.world
              link
              fedilink
              English
              arrow-up
              3
              ·
              9 months ago

              doesn’t allow you to do anything you can’t do without it.

              That’s false. It allows you to not need a password to unlock the volume at boot.

    • delirious_owl@discuss.online
      link
      fedilink
      arrow-up
      4
      ·
      9 months ago

      This. But not because the tech is sketch. because storing keys in a TPM is a disaster waiting to happen

      Did you make a backup of the key before storing it in the TPM? If not, then say goodbye to you data when the TPM fails.