security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

whitespace fixes

Browse Source
This commit is contained in:
Daniel Micay 2024-06-02 16:22:44 -04:00
parent 4b599c2421
commit 8c2aae1ddf
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
static/features.html
View File

@ -808,21 +808,22 @@
<section id="duress"> <section id="duress">
<h3><a href="#duress">Duress PIN/Password</a></h3> <h3><a href="#duress">Duress PIN/Password</a></h3>
<p>GrapheneOS provides users with the ability to set a duress PIN/Password that <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 will irreversibly wipe the device (along with any installed eSIMs) once entered
anywhere where the device credentials are requested (on the lockscreen, along anywhere where the device credentials are requested (on the lockscreen, along
with any such prompt in the OS).</p> 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 <p>The wipe does not require a reboot and cannot be interrupted. It can be set
at <b>Settings&#160;<span aria-label="and then">></span> Security&#160; up at <b>Settings&#160;<span aria-label="and then">></span> Security&#160; <span
<span aria-label="and then">></span> Duress Password</b> in the owner profile. aria-label="and then">></span> Duress Password</b> in the owner profile. Both a
Both a duress PIN and password will need to be set to account for different profiles duress PIN and password will need to be set to account for different profiles
that may have different unlock methods.</p> that may have different unlock methods.</p>
<p>Note that if the duress PIN/Password is the same as the actual unlock method, the <p>Note that if the duress PIN/Password is the same as the actual unlock method,
actual unlock method always takes precedence, and therefore no wipe will occur.</p> the actual unlock method always takes precedence, and therefore no wipe will
occur.</p>
</section> </section>
<section id="more-secure-fingerprint-unlock"> <section id="more-secure-fingerprint-unlock">
<h3><a href="#more-secure-fingerprint-unlock">More secure fingerprint unlock</a></h3> <h3><a href="#more-secure-fingerprint-unlock">More secure fingerprint unlock</a></h3>