My proposition is to make a softer option for the duress pin (possibly with some kind of warning in the corresponding settings menu that using it as a bypass for border checks will cause troubles). Could be called a "robber pin".
For instance, it could clear data of specific applications, remove specific files, etc., maybe remove a specific eSIM, and leave no visual traces that this option was ever configured. And keep working as normally, without making it look too suspicious.
This should be useful in case it's clear that the attacker has no access to the analysis tools, which could prove what exactly was removed.
GOS devs responses appear to be solely limited to those who are at risk of being checked with these tools. I think this doesn't make sense: you don't need any tools to know that the phone was just fully wiped, 'cause it kinda screams in the face with this fact currently:
https://www.androidauthority.com/grapheneos-duress-pin-us-prosecution-3691271/
I don't say that they've implemented something useless, though. It's useful for journalists in particular, who may be transporting some raw secret materials, just as one example.
> quiet a rare case
The meme I posted is an expression of my frustration with GOS devs ignorance of dozens of repetitive criticisms made by others, long before me.
GOS doesn't seem to respond to this particular kind of criticism on Nostr. They, however, at least used to respond on the platforms, where they in practice may threaten a critic with a ban (last paragraph):
https://discuss.grapheneos.org/d/17241-duress-pin-limited-usefulness/18
The thing I learned from all this, with the help of alp (npub175n…g6w0) in a completely unrelated discussion, is that this kind of criticism should never ever be mixed with the "social normality" kind of argumentation (including UX-related).
#grapheneos
codonaft
npub1al…7rg94
2026-08-06 16:45:56 GMT
in reply to nevent1q…2yfv
Author Public Key
npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94Published at
2026-08-06 16:45:56 GMTEvent JSON
{
"id": "01f896b3ced9b8569e56eba9b7f092195bb5788f7f9fd057513355e66cf10e3b",
"pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19",
"created_at": 1786034756,
"kind": 1,
"tags": [
[
"e",
"56b7bdae33c97e45750b00668acb68b750be4dffb4ac9b1592c48dee87e3e40c",
"",
"root"
],
[
"p",
"efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19"
],
[
"e",
"000075ce36cc1441444269ec4745c915304fe0441f7739c44be95cfb462bb4c0",
"",
"reply"
],
[
"p",
"b7cf9f42a796b091e843dce919d3ef4c0dc82e029452edf0bdbcdeb9ecb93e78"
],
[
"p",
"f527cf970ce260e74261214bf612e8f75a59db1835ed7e4053326c3f65e232ee",
"",
"mention"
],
[
"t",
"grapheneos"
]
],
"content": "My proposition is to make a softer option for the duress pin (possibly with some kind of warning in the corresponding settings menu that using it as a bypass for border checks will cause troubles). Could be called a \"robber pin\".\n\nFor instance, it could clear data of specific applications, remove specific files, etc., maybe remove a specific eSIM, and leave no visual traces that this option was ever configured. And keep working as normally, without making it look too suspicious.\n\nThis should be useful in case it's clear that the attacker has no access to the analysis tools, which could prove what exactly was removed.\n\nGOS devs responses appear to be solely limited to those who are at risk of being checked with these tools. I think this doesn't make sense: you don't need any tools to know that the phone was just fully wiped, 'cause it kinda screams in the face with this fact currently:\n\nhttps://www.androidauthority.com/grapheneos-duress-pin-us-prosecution-3691271/\n\nI don't say that they've implemented something useless, though. It's useful for journalists in particular, who may be transporting some raw secret materials, just as one example.\n\n\u003e quiet a rare case\n\nThe meme I posted is an expression of my frustration with GOS devs ignorance of dozens of repetitive criticisms made by others, long before me.\n\nGOS doesn't seem to respond to this particular kind of criticism on Nostr. They, however, at least used to respond on the platforms, where they in practice may threaten a critic with a ban (last paragraph):\n\nhttps://discuss.grapheneos.org/d/17241-duress-pin-limited-usefulness/18\n\nThe thing I learned from all this, with the help of nostr:npub175nul9cvufswwsnpy99lvyhg7ad9nkccxhkhusznxfkr7e0zxthql9g6w0 in a completely unrelated discussion, is that this kind of criticism should never ever be mixed with the \"social normality\" kind of argumentation (including UX-related).\n\n#grapheneos",
"sig": "6da097103071700a511c454b28a8ff44e27a55ec107c4cbdb31d7e880b79df4e81a63b43d62e040fb3b6279e9525108d2d8a30ed8c295d58c5c9d23b2ccaa081"
}