<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Duress on Side Of Burritos</title>
  <link rel="alternate" href="https://staging.sideofburritos.com/tags/duress/" />
  <link rel="self" href="https://staging.sideofburritos.com/tags/duress/index.xml" />
  <subtitle>Recent content in Duress on Side Of Burritos</subtitle>
  <id>https://staging.sideofburritos.com/tags/duress/</id>
  <generator uri="http://gohugo.io" version="0.165.0">Hugo</generator>
  <language>en-us</language>
  <updated>2026-07-30T13:45:00Z</updated>
  <author>
    <name>Josh</name>
    
  </author>
  
      <entry>
        <title>Arrested After Using GrapheneOS’s Duress PIN</title>
        <link rel="alternate" href="https://staging.sideofburritos.com/blog/arrested-for-using-duress-pin-grapheneos/" />
        <id>https://staging.sideofburritos.com/blog/arrested-for-using-duress-pin-grapheneos/</id>
        <published>2026-07-30T13:45:00Z</published>
        <updated>2026-07-30T13:45:00Z</updated>
        <summary type="html">The U.S. government has charged Samuel Tunick, alleging that he gave CBP officers a passcode that erased his phone when they entered it, preventing them from searching its contents.</summary>
          <content type="html"><![CDATA[<h2 id="-hahahugoshortcode29s0hbhb">🎥 


<a href="https://youtu.be/vz6OwDYDIaI" target="_blank" rel="noopener" class="text-break">Video Link</a></h2>
<hr>
<h2 id="links-referenced-for-video">Links referenced for video</h2>
<ul>
<li>


<a href="https://www.courtlistener.com/docket/71998357/united-states-v-tunick/" target="_blank" rel="noopener" class="text-break">https://www.courtlistener.com/docket/71998357/united-states-v-tunick/</a></li>
<li>


<a href="https://arstechnica.com/gadgets/2026/07/activist-charged-with-felony-after-giving-border-agent-duress-code-that-wiped-his-phone/" target="_blank" rel="noopener" class="text-break">https://arstechnica.com/gadgets/2026/07/activist-charged-with-felony-after-giving-border-agent-duress-code-that-wiped-his-phone/</a></li>
<li>


<a href="https://www.404media.co/the-government-hopes-to-set-a-precedent-an-interview-with-the-man-charged-for-allegedly-wiping-his-grapheneos-phone/" target="_blank" rel="noopener" class="text-break">https://www.404media.co/the-government-hopes-to-set-a-precedent-an-interview-with-the-man-charged-for-allegedly-wiping-his-grapheneos-phone/</a></li>
<li>


<a href="https://en.wikipedia.org/wiki/Stop_Cop_City" target="_blank" rel="noopener" class="text-break">https://en.wikipedia.org/wiki/Stop_Cop_City</a></li>
<li>


<a href="https://en.wikipedia.org/wiki/January_6_United_States_Capitol_attack" target="_blank" rel="noopener" class="text-break">https://en.wikipedia.org/wiki/January_6_United_States_Capitol_attack</a></li>
<li>


<a href="https://www.youtube.com/watch?v=JTurSi0LhJs" target="_blank" rel="noopener" class="text-break">https://www.youtube.com/watch?v=JTurSi0LhJs</a></li>
</ul>
<hr>


<p><details >
  <summary markdown="span">Transcript</summary>
  <h3 id="transcript">Transcript</h3>
<p><strong>Please excuse any grammatical errors. I used a tool to generate the transcript and haven&rsquo;t had a chance to read through it yet.</strong></p>
<hr>
<p>So today what I want to talk about is the case of United States versus Tunick. This is regarding the use of the duress pin on Graphene OS. I thought we could start off by just reading the official indictment against Tunick before covering some other nuances in this case.</p>
<p>So on or about January 24th, 2025, in the Northern District of Georgia, the defendant Samuel Tunick, before and during the search for and seizure of property by Customs and Border Patrol Tactical Terrorism Response Team, Supervisory Officer L.CDOT, a person authorized to make such search and seizure, did knowingly destroy, damage, waste, dispose of, and otherwise take any action to delete the digital contents of a Google Pixel cellular phone for the purpose of preventing and impairing the government&rsquo;s lawful authority to take said property into its custody and control in violation of Title 18, United States Code, Section 2232A.</p>
<p>So the first thing I want to say about this is regarding the knowingly destroy, damage, waste of, dispose, delete digital contents part. The way the duress pin works on Graphene OS is when you enter that pin, it initiates the sequence, which deletes the keys that are used to decrypt the data on the device. Those keys are used to decrypt the data on your device when you correctly enter the pin and they&rsquo;re stored on the secure element.</p>
<p>So it&rsquo;s the keys that were deleted on the device, not the actual data. For all intents and purposes, that data is now permanently inaccessible, but the data was not actually deleted. Again, like I said, this is a very nuanced point, but the law loves nuances.</p>
<p>I was trying to think of a good analogy for this. So imagine the lock you have on your house. You insert the key, you open the lock, you can access your home&rsquo;s contents. Entering the duress pin is equivalent to changing the pins on the tumbler inside the lock on the door. So now when you insert the key into the lock, the key no longer works because the pins have changed. At that point you can&rsquo;t access your home, but everything inside is just as you left it. It&rsquo;s just the key no longer works.</p>
<p>I&rsquo;m not a lawyer, but that doesn&rsquo;t sound like it was destroyed. I guess we&rsquo;ll see how that plays out. So that&rsquo;s the initial indictment. I&rsquo;ll link this down below if you want to keep up with the court case. The latest item was released on July 20th, 2026.</p>
<p>But at this point there&rsquo;s been a bunch of articles published on this topic, and the first one I want to talk about is one from Ars Technica. So in early 2025, like we saw in the initial indictment, Atlanta resident Samuel Tunick was on his way home following a trip abroad. After landing in the U.S., customs agents demanded access to his Pixel phone, which was running an alternative version of Android called Graphene OS.</p>
<p>And rather than handing over his data, Tunick used a clever feature of the software to delete everything, which again is the duress pin. He actually told the border patrol agents his duress pin, they entered it, and the data was erased.</p>
<p>During their interrogation, CBP agents told Tunick they wanted to search his phone for evidence of child sexual abuse, and if he didn&rsquo;t unlock the device, it would be confiscated. Unless you are the Catholic priest from the town where I grew up who was charged and convicted of possession of CSAM—you know what they say, it&rsquo;s always the ones you most suspect—then these types of searches for everyday individuals are usually just fishing expeditions.</p>
<p>It&rsquo;s an excuse to protect the children, like we&rsquo;ve heard dozens of times, and the thing that kind of backs that up is this is what CBP told him, but it turns out it&rsquo;s because he was part of a group called Defend the Atlanta Forest, which opposed the construction of an enormous law enforcement training facility in the area, often known as Cop City. So this is what actually landed him on a list and got him detained at the airport.</p>
<p>But it just kind of makes me laugh that they followed the typical procedure of accusing someone of possessing CSAM, and that&rsquo;s why they&rsquo;re doing the search, and in order to protect the children, please unlock your device.</p>
<p>Tunick also claims he was never read his rights and requested legal counsel several times, but the requests were denied. He was at a border area. He was re-entering the U.S., and a lot of rights are sort of in a legal gray zone at that point, which is why they can conduct these warrantless search and seizures.</p>
<p>The other article which has some great points is one from 404 Media. If you haven&rsquo;t heard of them before, check them out. They put out some really good content.</p>
<p>The agents tried to rig this game by making this all come to a head at the airport, he added. Ordinarily, authorities would need a warrant to search the contents of someone&rsquo;s phone, but at an airport, those protections often do not apply. They could have asked a judge for a search warrant for Sam&rsquo;s phone if they thought they had evidence for a crime. They didn&rsquo;t do that.</p>
<p>CBP said all travelers are subject to inspection and ensure compliance with the U.S. laws. These inspections, including questioning and rare search of electronic devices, are conducted on a case-by-case basis, taking into account factors such as travel history and law enforcement alerts.</p>
<p>And speaking of those alerts, Department of Homeland Security, also known as DHS, called the airport ahead, said Tunick was coming through, and asked officers to stop him. “We want you to get his phone and search his phone,” the officers said.</p>
<p>So a lot of this keeps going back to Graphene OS, the use of the duress pin, which I think is great. It&rsquo;s a fantastic feature. I think it&rsquo;s also worth remembering that the reason Tunick is in this situation is because he legally participated in a protest, which happened to land him on a list that got him stopped at the airport.</p>
<p>So while some protests will get you on a list that gets you detained, other protests, at least I think it was a protest, will get you a presidential pardon.</p>
<p>Regardless, if you&rsquo;re in the United States, I think this video from the Pot Brothers at Law has some really good advice if you are detained.</p>
<p>And they ask more questions? Am I being detained or am I free to go? And if detained, what do you say? I invoke the fifth. And then what do you do? You shut the fuck up.</p>
<p>Now, whether or not you should enter the duress pin if you are detained, I guess we&rsquo;ll see how this case goes and see if it is a legal thing to do. Again, if you want to keep up with the case, I will link this down below so you can check for updates.</p>
<p>I do think this is one of the most important cases when it comes to privacy in recent years. So I&rsquo;m extremely curious to see how this goes. When there are updates, I will make some future videos on it. But until then, hope you have a great rest of your day, and I&rsquo;ll see you next time.</p>

</details></p>

]]></content>
      </entry>
      <entry>
        <title>How to set up Duress PIN/Password on GrapheneOS</title>
        <link rel="alternate" href="https://staging.sideofburritos.com/blog/grapheneos-duress-pin-password/" />
        <id>https://staging.sideofburritos.com/blog/grapheneos-duress-pin-password/</id>
        <published>2024-08-19T10:00:00Z</published>
        <updated>2024-08-19T10:00:00Z</updated>
        <summary type="html">A few months ago, GrapheneOS released the Duress PIN/Password feature. In this video, I&amp;#39;ll describe some caveats about the feature, walk you through the setup, and show you what it looks like when you enter it to wipe the device.</summary>
          <content type="html"><![CDATA[<h2 id="-hahahugoshortcode60s0hbhb">🎥 


<a href="https://youtu.be/Q7oM0IB-IiM" target="_blank" rel="noopener" class="text-break">Video Link</a></h2>
<hr>
<h2 id="links-referenced-for-video">Links referenced for video</h2>
<ul>
<li>


<a href="https://grapheneos.org/features#duress" target="_blank" rel="noopener" class="text-break">https://grapheneos.org/features#duress</a> - GrapheneOS Duress PIN/Password documentation</li>
<li>


<a href="https://monogr.ph/665ae7b0571fecfdc8c3bdb0/" target="_blank" rel="noopener" class="text-break">https://monogr.ph/665ae7b0571fecfdc8c3bdb0/</a> - QA of GrapheneOS Duress PIN/Password feature</li>
<li>


<a href="https://yellowball.fm" target="_blank" rel="noopener" class="text-break">https://yellowball.fm</a> - 🟡 Yellowball, no BS podcast hosting</li>
</ul>
<hr>
<h3 id="transcript">Transcript</h3>
<p><strong>Please excuse any grammatical errors. I used a tool to generate the transcript and haven&rsquo;t had a chance to read through it yet.</strong></p>
<p>I finally found my battery, so I can start recording videos again. The feature I want to talk about today is the duress PIN/password feature that GrapheneOS released a few months ago. First, we&rsquo;ll start by looking at the documentation, and then I&rsquo;ll show you how to set it up on a device and what the actual wipe process looks like once you enter the duress PIN/password.</p>
<p>Looking at the official documentation, which is always the best place to go first, I will link that down below. GrapheneOS provides users with the ability to set a duress PIN/password that will irreversibly wipe the device along with any installed eSIMs. Once entered, anywhere the device credentials are requested, such as the lock screen or any other prompt that the OS shows you asking for your PIN or password, the wipe does not require a reboot and cannot be interrupted. So once it&rsquo;s entered, all data on your device is completely inaccessible, and you will never have access to it again. Take that as a warning—be careful with this. Once you set it, do not enter it just to test for any reason whatsoever, because all your data will be gone.</p>
<p>Both a duress PIN and password are needed to account for the different unlock methods that user profiles may use. You might have one user profile with a PIN and another with a password, which is why you need to set both. It&rsquo;s important to note that if your duress PIN is the same as your actual unlock PIN, the actual unlock PIN will take precedence. So, let&rsquo;s say your duress PIN is 1234 and your unlock PIN is also 1234—once you enter 1234 into your device, it will be unlocked, and you will not wipe the device.</p>
<p>One more thing I want to mention before I get into the live demo: make sure you check into any local laws or regulations regarding this feature. If you&rsquo;re at the airport and they ask you for your PIN, and instead, you enter this and your device is wiped, who knows what could happen. Destruction of evidence could be one of many legal implications. So, make sure you understand the ramifications of using this feature, wherever you are in the world, before actually using it.</p>
<p>With that out of the way, let&rsquo;s check out what this actually looks like. Here, I have a Google Pixel with GrapheneOS installed. The only thing I&rsquo;ve done is set a PIN code, which is 12345. In order to set a duress PIN/password according to the documentation, we go into Settings, scroll down to Security, and then we go to Duress Password. We need to enter our device PIN to authenticate that it&rsquo;s us. Once you finish reading the text on the page, you can select the duress PIN. I&rsquo;m going to set the PIN to 1111 and the password to qqqq. Once we select &ldquo;Add,&rdquo; again, you&rsquo;ll see a warning about what will happen if you enter this. Select &ldquo;Proceed,&rdquo; and now on this screen, you can either update your duress PIN or password or delete it.</p>
<p>So now, let&rsquo;s see what the actual wipe looks like. We&rsquo;re all pretty familiar with the lock screen—if you enter it there, the phone will be erased. To show you a little more non-standard scenario, if we go into Settings and back to Security, in order to set a fingerprint, you have to enter your device PIN. We&rsquo;re going to select the fingerprint unlock, and now this is an example of the OS prompting us for our PIN. Instead of entering my actual PIN, I&rsquo;m going to enter my duress PIN. You&rsquo;ll see it says &ldquo;Wrong PIN,&rdquo; the device powers off, and the irreversible wipe has occurred along with wiping all installed eSIMs. At this point, you can power the device back on. Just give it a minute to power up. This is the screen you&rsquo;ll see after the wipe occurs. You can go down to the factory reset. It&rsquo;s important to note that this feature does not brick the device in any way; it just makes the data completely inaccessible. So, we select the option for factory reset, confirm that, and now we have a fresh installation of GrapheneOS.</p>
<p>Whether or not this feature is applicable to you and your threat model is a personal decision and something you need to decide. I would caution against setting it to something simple like 1234. If someone has your device and, as a joke, they enter that PIN, now your device is wiped, and that would not be good. I do want to point out one other site that I think someone posted on the GrapheneOS forum. Someone did some duress password QA testing—they just went through a bunch of different scenarios to test it out. I thought it was something cool to check out, so I&rsquo;ll link that down below. One other use I saw someone mention for this feature is: you take a piece of paper, write your duress PIN code on it, and put it in your phone case. If someone finds your phone and they think you just left your PIN code in there because you&rsquo;re forgetful, they&rsquo;ll enter it, and your device is wiped. That&rsquo;s one option I like—that&rsquo;s something to consider.</p>
<p>So, for the last year, I wanted to start a podcast, and when I started looking at where I could host it, I couldn&rsquo;t really find an option that had everything I was looking for from a privacy perspective. So instead, I decided to build that, and it&rsquo;s called Yellowball. You can check it out at yellowball.fm. I would appreciate it if you could sign up and test it out. Let me know if you find any bugs—all you need to sign up is a username and a password. I know many of you are not looking to start a podcast, but if you&rsquo;re like me, then in your friends and family, you&rsquo;re likely the go-to person when someone has a tech question. So, if someone comes to you and asks about starting a podcast, if you could suggest they check out Yellowball, I would really appreciate it. Keep an eye out because in the next one to two weeks, I&rsquo;ll be publishing the first episode of my podcast, which is going to be called In the Shell. It&rsquo;s going to feature different stories from tech, different events that have happened in the past, and things I find interesting. So, if you&rsquo;re watching this video a week or two after it&rsquo;s been published, check down below—I&rsquo;ll link it in the description. If you have any questions or comments, feel free to leave those down below, and I&rsquo;ll see you next time.</p>
]]></content>
      </entry>

</feed>
