The border agents didn't act in good faith, regardless of what they're empowered to do. They wanted the data for one reason and fabricated another to prompt the device search. The data they were interested in pertained to protest activity protected under the constitution but the lie they told was about something criminal. That anything within 100 miles of the border is constitution free tosses that out, I guess, but…
GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
121–130 of 206 posts
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#122Earlier quoted context omitted.
The level of duress also matters. US citizens have been shipped to foreign prisons and there's an active case of high-level officials at DOJ violating court orders about that.
> US citizens have been shipped to foreign prisons From US soil?
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#123Then when in travel, and about to pass a border, you enter that selective mode. You can enter a different password as the proxy to unlock the phone in this bare minimal data mode. The agents can access it, etc but wont have all the data. That data shouldn't even be visible in the OS, and if they try to copy the hard drive they will get encrypted data in the other blocks.
You still legally comply with orders and unlock the phone but the other partitions don't unlock/decrypt unless you specifically unlock them.
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#124This should be an interesting case in today’s legal climate Obviously grafeneOS has no liability. But the owner of the device didn’t take the action to remove the data, the CBP officer entered it. We already have some precedent around being forced to give up your password. How does that change if you are forced to give up a password that is destructive? What if the password works fine at home and the same password do…
Could you be charged with destruction of evidence?
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#125Earlier quoted context omitted.
See also, 5th amendment. They can't just declare on the spot that your data is now their data.
The 4th ammendemnt is the one that protects your data and other possessions in general, not the 5th. The 5th protects you from being compelled to give testimony that might incriminate you, which then protects you from being compelled to offer a password to access data that could be used to incriminate you. Since 4th ammendemnt protections are significantly curtailed at border crossings, they can actually declare on t…
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#126The border agents didn't act in good faith, regardless of what they're empowered to do. They wanted the data for one reason and fabricated another to prompt the device search. The data they were interested in pertained to protest activity protected under the constitution but the lie they told was about something criminal. That anything within 100 miles of the border is constitution free tosses that out, I guess, but…
[flagged]
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#127The founding fathers would be aghast at what America became. Hard to imagine modern America passing some of those constitutional amendments that older America passed wayyy back.
On the other hand, why care what the American founding fathers thought? There have been two centuries since then of developments in democratic countries that some Americans could choose as a model they like more. And now it's the Chinese century anyway.
Because they had direct experience with tyranny and exploitation, and documented their response to that in the US founding documents. We care because if you don't learn from history, you're doomed to repeat it. Which is pretty much what's happening right now.
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#128As a GrapheneOS user and a U.S. citizen that cares about the constitution, I fully support the actions taken by the individual
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#129This should be an interesting case in today’s legal climate Obviously grafeneOS has no liability. But the owner of the device didn’t take the action to remove the data, the CBP officer entered it. We already have some precedent around being forced to give up your password. How does that change if you are forced to give up a password that is destructive? What if the password works fine at home and the same password do…
You put a sticky note with the duress PIN on your phone. When detained, the officer notices a PIN in plain sight on the phone, enters it, and the phone wipes itself. You were never asked for a PIN. Could you be charged with destruction of evidence?
IANAL but I expect it depends on whether someone thinks they can prove your intent was specifically to disrupt a (legitimate) search.
To recycle a comment from 2 days ago, regarding why one might reasonably have the duress code written on the phone:
> "Your honor, I have the real pin memorized because I use it all the time, but since I can never use the duress code, I had to keep it somewhere handy."
> Or
> "Pickpocketing and phone-snatching is a real problem overseas, I put it there so that criminal would wipe the phone trying to get in, denying them access to things like my bank account."
> Heck, those aren't just plausible, they might be a good idea.
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#130Earlier quoted context omitted.
similar to structuring laws, right? trying to not provide evidence is occasionally similar to destroying it.
yes, this is what I'm leaning towards. if intent (without accusation!) is the issue, then not providing access seems the same as removing or denying access. they're trying to do this kind of thing for foreigners (no social media account -> no entry: https://www.cnbc.com/2025/12/10/us-to-inspect-tourists-socia... ), this feels like a grab at applying it to citizens too. if someone is accused of something (possibly ret…