this post was submitted on 01 Sep 2026
199 points (96.7% liked)
Technology
87833 readers
3263 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
This is why threat modeling is important.
Chances are they can clone the eMMC and wait for a CVE. Or threaten or hold you until you cave. If a lawsuit is your only recourse, I would expect any constitutional barriers to be ignored in practice. Your best bet is to never end up being an explicit target, which may be more difficult for certain individuals.
My threat model considers dragnet surveillance as the primary threat, so I'd compromise on surviving dirty maid type attacks in favor of reducing the information my device gives out.
Obviously if your device is being actively exploited, you cannot be private. But your security requirements increase greatly if your data footprint indicates to them that you warrant targeted scrutiny.
100% agree with you, for who I am and what I do I know that I need a device that is as tamper resistant as possible with the smallest attack surface feasible. That goes for remote execution as much as the evil maid scenario. But this is entirely catered to my threat model and risk tolerance. And sure there is the possibility of the rubber hose cryptanalysis but that doesn't mean we should give up on securing as much as possible on the device side. It's the swiss cheese model and we're plugging a hole at a time lol
I advocate for everybody to use as secure a device as practical, and for these mitigations to be the default, but I'm fundamentally speaking for myself in this thread with my stance on fairphone and /e/OS right now. I want to support repairability and ethical supply chains too without compromising on my more core tech needs