• Object@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      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
        1
        ·
        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
          1
          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.

    • Rooki@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      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
        1
        ·
        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

    • surewhynotlem@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      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.

    • Lembot_0002@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      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.

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

        Yeah, nothing important. Just your banking apps, personal documents, photos, government apps, emails, all the services linked to your phone via mobile number, personal chats, work chats, 2fa codes, some other not important stuff. But at least it doesn’t have your games. Unless you play games on your phone, then you are fucked.

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

          If they don’t save those photos somewhere else from time to time, it means those photos aren’t that important.