• Object@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      23
      arrow-down
      1
      ·
      2 days ago

      One major difference is that it is so much easier to lock yourself out of the desktop TPM chip compared to mobile device security chips because they’re not tightly coupled.

      • acosmichippo@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        and phones make you use your unlock pin often, so people are forced to remember it. on the other hand windows lets you use a short pin instead of your full account password pretty much forever which results in people forgetting the password completely.

        • Rooki@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          2 days ago

          That isnt even the part it is encrypted, the TPM encryption is either “Automatic” or over a password (any length) on startup so far i know it from my work with Bitlocker (tpm 2.0) on windows 10. Idk if this is different on windows 11.

    • surewhynotlem@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      2 days ago

      Huh … I never noticed. Probably because my phone OS never failed to boot, requiring me to pull data off the HDD directly.

    • OfficerBribe@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      2 days ago

      Android I think just uses same credentials you use to unlock account, at least I am not aware of any recovery key. And you are prompted for credentials from time to time so it is harder to forget. I use fingerprint as main unlock + pattern and I have to enter pattern roughly once a week I think.

      On Windows if you set up Windows Hello (fingerprint or PIN usually), you are not reminded to enter password afterwards so eventually you can forget it. And if you do not know your password and cannot recover account, you will not be able to retrieve BitLocker recovery key. So fix to this problem could be another annoyance to users if it would be implemented as Android does it.

    • Rooki@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      2 days ago

      The only phone manufacture that does that is Google with pixel. Any other phone is for my knowledge either “weakly” encrypted or not at all.

      Still your Mobile OS isnt just upgrading and encrypting your SD card and main drive. Thats the point.

      • InnerScientist@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        All devices launching with Android 10 and higher are required to use file-based encryption.

        To use the AOSP implementation of FBE securely, a device needs to meet the following dependencies:

        • Kernel Support for Ext4 encryption or F2FS encryption.
        • Keymaster Support with HAL version 1.0 or higher. There is no support for Keymaster 0.3 as that does not provide the necessary capabilities or assure sufficient protection for encryption keys.   
          
        • Keymaster/Keystore and Gatekeeper must be implemented in a Trusted Execution Environment (TEE) to provide protection for the DE keys so that an unauthorized OS (custom OS flashed onto the device) cannot simply request the DE keys.   
          
        • Hardware Root of Trust and Verified Boot bound to the Keymaster initialization is required to ensure that DE keys are not accessible by an unauthorized operating system.

        https://source.android.com/docs/security/features/encryption/file-based?hl=en

    • Lembot_0002@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      24
      ·
      2 days ago

      Most people don’t have anything of importance on their phones. And the tuning options are almost absent on phones, so it is less problematic bug-wise.