Update documentation to account for Safety Center UI

This commit is contained in:
matchboxbananasynergy
2024-08-22 18:39:14 +00:00
committed by Daniel Micay
parent fca5cdf296
commit 7b6b2b5bbd
3 changed files with 19 additions and 12 deletions

View File

@@ -376,7 +376,8 @@
<p>GrapheneOS disables showing the characters as passwords are typed by default. You
can enable this in <b>Settings&#160;<span aria-label="and then">></span>
Privacy</b>.</p>
Security &amp; privacy&#160;<span aria-label="and then">></span> Privacy&#160;<span
aria-label="and then">></span> Show passwords</b>.</p>
<p>Third party accessibility services can be installed and activated. This
includes the ones made by Google. Most of these will work but some may have a hard
@@ -813,8 +814,9 @@
for each boot via the shared randomized values.</p>
<p>This feature can be disabled via <b>Settings&#160;<span aria-label="and
then">></span> Security&#160;<span aria-label="and then">></span> Secure app
spawning</b> if you prefer to have faster cold start app spawning time and lower
then">></span> Security &amp; privacy&#160;<span aria-label="and then">></span>
Exploit protection&#160;<span aria-label="and then">></span> Secure app spawning</b>
if you prefer to have faster cold start app spawning time and lower
app process memory usage instead of the substantial security benefits and the
removal of the only known remaining direct device identifiers across profiles (i.e.
not depending on fingerprinting global configuration, available storage space, etc.
@@ -1250,7 +1252,8 @@
prevent inspecting or modifying the app in a weak attempt to hide their code and API
from security researchers. GrapheneOS allows users to disable <b>Native code
debugging</b> via a toggle in <b>Settings&#160;<span aria-label="and then">></span>
Security</b> to improve the app sandbox and this can interfere with apps debugging their
Security &amp; privacy&#160;<span aria-label="and then">></span> Exploit protection</b>
to improve the app sandbox and this can interfere with apps debugging their
own code to add a barrier to analyzing the app. You should try enabling this again if you've
disabled it and are encountering compatibility issues with these kinds of apps.</p>