538
this post was submitted on 26 Aug 2026
538 points (99.1% liked)
Technology
87598 readers
3788 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That privacy was already long gone by the time of this case.
https://www.law.cornell.edu/uscode/text/18/2232
If he hadn't used duress and had just refused, he'd have been fine. Graphine is secure and would have had his back
If he hadn't given them the code and instead left it in his wallet, and they did it themselves, he'd have been fine.
All he had to do was plead the 5th.
He's going to get hit with a felony for destroying data to prevent a search. There are tons of precedents in the 11th Circuit for searching without a warrant.
A duress password is only useful if what you'd be facing is worse than 18 U.S. Code § 2232a, and then only if they don't have enough to convict you already.
https://www.youtube.com/watch?v=_2rokxux5cU`___`
Dude is just protesting the construction of a large cop training facility near him. I don't know what the fuck he did to get on the FBI radar, but I wish him good luck; he's gonna need it.
Graphene devs fucked over this guy. They should apologize
When Graphene is serious, the duress passcode will QUIETLY wipe your phone and leave it looking normal, preferably with normal-looking innocuous photos, media, etc.
This is what happens when devs aren't really thinking about the real world use case.
They shouldn't apologize, the dude should of known that destroying evidence during an investigation is going to land you in jail.
No. If you make and distribute security-related software, you should consider the safety of your user.
Your threat model absolutely should include this exact scenario. And you should know enough to understand and implement principles like plausible deniability and repudiation.