this post was submitted on 14 Jun 2025
41 points (97.7% liked)
Privacy
38823 readers
888 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It means they can rip the encrypted data off the phone, then take it over to a system with a bunch of GPUs and brute-force the password.
But isn't the key supposed to be in the "Secure Element" (or whatever they call it)?
It's possible that they discovered a weakness in the way the keys are generated in the TPM (or whatever it's called for Android), which brings the time to brute force down from 1,000 years to a few weeks with massive GPUs?
Similar story, as of a few years ago, OpenSSH announced deprecating support for RSA keys keys because of a vulnerability in SHA-1 hashing, where they cited research showing a determined attacker could break the key with $50k of compute power, which may seem like a lot, but is pretty feasible, necessitating the deprecation
I don't know about the Android system, but during the initial design and fabrication, the hardware may have not been designed to withstand the compute power just a few years later, and can not be easily updated to improve the security. These are the weaknessed Cellebrite is looking for.
Interesting. I figured there was just a backdoor in Knox or iOS it was using.