GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
1–10 of 206 posts
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#2Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#3Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#4Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#5Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#6US Government targets Cop City protester over phone operating system
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#7Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#8Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#9Obviously 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 does a wipe based on location? Either way, the user complied, and did not take action to wipe their device.
Re: GrapheneOS Defends Data-Wiping Function That Blocked US Border Search
#10Someone who is a lawyer knows any details about the US justice systems precedents with regards to the fifth amendmend (regards to self incrimination) vs obstruction of justice (by destroying evidence) as would be applicable to a duress wipe? Also would the distinction of being (or not) read their miranda rights and placed under arrest in this case make a difference as to the status of any possible obstruction?