• Nonononoki@lemmy.world
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    1 day ago

    LUKS encrypts the whole drive, native FS encryption can encrypt it partially (e.g. just the home partition). Additionally, decrypting without a keyboard is a pain or impossible (e.g. touch screen only devices).

    • RichardTickler@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      17 hours ago

      If the home/root partition is a physical or logical volume you most certainly can leave that decrypted while encrypting other volumes. The system could not boot if that were the case as the efi partition cannot be encrypted.

    • Petter1@lemm.ee
      link
      fedilink
      arrow-up
      5
      ·
      22 hours ago

      PostmarkedOS was able to encrypt disk while offering on screen touch keyboard to unlock it on my pinePhone “pro”.

      • Natanael@infosec.pub
        link
        fedilink
        arrow-up
        7
        ·
        21 hours ago

        It does this by encrypting the OS separately from apps and user data. The OS is auto unlocked (usually using a hardware TPM chip).

    • prole@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      22 hours ago

      I’m the furthest thing from an expert in linux encryption, but can you not use KDE’s “Vaults” feature to create encrypted folders/drives? I think it uses “CryFS” as the backend (according to KDE. Don’t really know enough about it).

      I’ve used them on my btrfs drive and seemed to work fine.

      • Natanael@infosec.pub
        link
        fedilink
        arrow-up
        7
        ·
        21 hours ago

        The boot order of the component which handle encryption has an effect on which other system components which reliably can be scripted to automate stuff with that data.

        Tldr if it’s just for your documents, sure. If you’ve got sensitive program data / config there, it makes it harder to autostart them because now you have to wait.