New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Banking apps not working #651
Comments
You'll need to gather logs with either the developer options bug report capture tool or |
If you use the bug report capture tool, note that it captures a huge amount of data including sensitive data. You can either extract the relevant logs from the zip file it generates yourself or send the zip to us over Matrix or via an email to contact@grapheneos.org. You're free to remove nearly all the information from the zip. Only the logs are relevant, which are in a single dedicated text file, and we really only need the logs for where the app is launched. |
So, for example like this? I filtered the output with
|
I don't really see a critical error there. Can you try to get all the nearby logs rather than filtering it that way? |
Please enable the "Native debugging toggle" in Settings under Security. That may fix the app you posted a log for. @lippling |
It looks like it's just trying to read the sysctl value rather than actually trying to use ptrace. It could be dying because of using ptrace but it's not shown in the log. |
Wow. It works. Thanks! But why? What are the implications of this setting? |
Are all of them working fine? Native debugging disables native code debugging via ptrace for tracing processes. It's normally used by developers but some apps use it as an incredibly weak form of anti-debugging / anti-tampering. Glad this is working for you now. |
Yes, all apps are working now. So it makes sense to enable |
Disabling native debugging improves the app sandbox and sandboxing elsewhere in the OS. It's up to you if you consider it worthwhile to disable it when you aren't using them. GrapheneOS leaves it enabled by default and just provides the option to disable it since it's a nice way of improving sandboxing and protecting against local privilege escalation. It's not a huge security benefit. It just disables the ability to use the It's simply a global toggle right now because in theory it should only be needed by developers who need to do debugging. It's unfortunate that there are apps using native code debugging as a strange way of trying to put up barriers to analysis of the apps. They aren't really accomplishing anything by doing that beyond slightly annoying security researchers who look into the apps. |
Ok, thanks for your detailed answer. Very much appreciated. |
I have installed different banking apps which generate TANs in addition to > 50 apps which are all are working perfectly so it must be an issue with these individual apps.
Google Play Services are also installed and I also tried a second profile where I didn't install Google Play Services. No difference.
de.fiduciagad.securego.vr
: logocom.starfinanz.mobile.android.dkbpushtan
: blank screende.fiducia.smartphone.android.securego.vr
: blank screende.postbank.bestsign
: works perfectlyCan I somehow provide additional help as these apps are important to me and this issue forces me to still use my iPhone.
The text was updated successfully, but these errors were encountered: