clarify why we support disabling native debugging
This commit is contained in:
parent
ea09a1d6e6
commit
cebc4d5219
@ -782,10 +782,10 @@
|
||||
<p>Many of these apps have their own crude anti-tampering mechanisms trying to
|
||||
prevent inspecting or modifying the app in a weak attempt to hide their code and
|
||||
API from security researchers. GrapheneOS allows users to disable native code
|
||||
debugging via a toggle in Settings ➔ Security 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>
|
||||
debugging via a toggle in Settings ➔ Security 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>
|
||||
|
||||
<p>Banking apps are increasingly using Google's SafetyNet attestation service to
|
||||
check the integrity and certification status of the operating system. GrapheneOS
|
||||
|
Loading…
x
Reference in New Issue
Block a user