this post was submitted on 02 May 2025
381 points (87.4% liked)

Technology

69702 readers
4021 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Rooki@lemmy.world 38 points 2 days ago (1 children)

Yeah it can happen, when you force people without their consent encrypting their data.

[–] Melonpoly@lemmy.world 16 points 2 days ago (6 children)

Isn't that what Iphone and Android already do?

[–] Object@sh.itjust.works 22 points 2 days ago (1 children)

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 2 points 2 days ago (1 children)

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 1 points 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 9 points 2 days ago (1 children)

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

[–] Landless2029@lemmy.world 6 points 2 days ago

Samsung is notorious for this.

[–] OfficerBribe@lemm.ee 3 points 2 days ago* (last edited 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 1 points 2 days ago (1 children)

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 2 points 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

[–] MonkderVierte@lemmy.ml 1 points 2 days ago* (last edited 2 days ago)

Different threat model and usage scenario. See the spilled milk comment.