From cebc4d5219ffca4df310b88fbb57e3ea031476cf Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Sat, 11 Sep 2021 06:07:36 -0400 Subject: [PATCH] clarify why we support disabling native debugging --- static/usage.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/static/usage.html b/static/usage.html index d9831246..a146f2cc 100644 --- a/static/usage.html +++ b/static/usage.html @@ -782,10 +782,10 @@

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.

+ 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.

Banking apps are increasingly using Google's SafetyNet attestation service to check the integrity and certification status of the operating system. GrapheneOS