From 204585866657fd2109f516ec1be36162126231d1 Mon Sep 17 00:00:00 2001
From: matchboxbananasynergy
 <107055883+matchboxbananasynergy@users.noreply.github.com>
Date: Sun, 2 Jun 2024 07:19:30 +0000
Subject: [PATCH] Initial features page documentation on duress password

---
 static/features.html | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/static/features.html b/static/features.html
index 32a35337..1ad77505 100644
--- a/static/features.html
+++ b/static/features.html
@@ -105,6 +105,7 @@
                             <li><a href="#supports-longer-passwords">Supports longer
                             passwords</a></li>
                             <li><a href="#auto-reboot">Auto reboot</a></li>
+                            <li><a href="#duress">Duress PIN/Password</a></li>
                             <li><a href="#more-secure-fingerprint-unlock">More secure fingerprint
                             unlock</a></li>
                             <li>
@@ -772,6 +773,23 @@
                     panic which leads to a reboot.</p>
                 </section>
 
+                <section id="duress">
+                    <h3><a href="#duress">Duress PIN/Password</a></h3>
+
+                    <p>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 where the device credentials are requested (on the lockscreen, along 
+                    with any such prompt in the OS).</p>
+
+                    <p>The wipe does not require a reboot and cannot be interrupted. It can be set up 
+                    at Settings > Security > Duress Password in the owner profile. Both a duress PIN 
+                    and password will need to be set to account for different profiles that may have 
+                    different unlock methods.</p>
+
+                    <p>Note that if the duress PIN/Password is the same as the actual unlock method, the 
+                    actual unlock method always takes precedence, and therefore no wipe will occur.</p>
+                </section>
+                
                 <section id="more-secure-fingerprint-unlock">
                     <h3><a href="#more-secure-fingerprint-unlock">More secure fingerprint unlock</a></h3>