banking-apps-compat-report

Hm, what's the definition of works? https://github.com/PrivSec-dev/banking-apps-compat-report/is... - closed without a fix for Zelle. Another user later opened a ticket about Zelle not working, and it got closed as a dupe of the first, which had been closed 2-3 years earlier. Not promising.

There's five banking apps that support it specifically listed here [1]. I guess the dozen is not listed somewhere. Roblox, Hyundai, and Kia are also apps that officially support GrapheneOS. We should note that not all that are supporting it are using attestation. I find all the people complaining about this to be rather insane. This is a completely open source linux distro getting official support from banks, some of the most legacy companies of all. This is good news. If companies are open-minded enough to support GrapheneOS, they're gonna be much more likely to also officially support other secure operating systems that are open source. These are banking apps that weren't previously possible to be used on GrapheneOS. We're going from zero to one, not a step back. [1] https://github.com/PrivSec-dev/banking-apps-compat-report/is...

Yep. Not sure all of them are attesting GrapheneOS, but there's at least 5 banks officially supporting it. https://github.com/PrivSec-dev/banking-apps-compat-report/is...

The trouble is that banking apps will not work if you degoogle your phone. GrapheneOS was an attempt to make this sort of thing work, in a phone OS more secure than stock Android But to be honest, many banking apps randomly stop working with GrapheneOS anyway. So if you see this... https://privsec.dev/posts/android/banking-applications-compa... https://github.com/PrivSec-dev/banking-apps-compat-report And check the issues, it's unpredictable whether a bank will continue to work with GrapheneOS So.. if you accept GrapheneOS might not be reliable for this use case, and decide have two phones (one just for banking stuff, another for.. using), then degoogling is fine. Only thing is that the banking device probably needs to be a phone (or tablet I guess), I don't think you can emulate a real device good enough for it to work on something like

PayPal still works on GrapheneOS. It's because PayPal shipped an update with incorrect anti-tampering code incompatible with secure app spawning. It can be worked around with the per-app secure app spawning toggle until they fix it. Starling Bank app still works on GrapheneOS too. See here: https://github.com/PrivSec-dev/banking-apps-compat-report/is...

"Most" seems quite inaccurate. There is a Graphene OS banking app compatibility database [here](https://github.com/PrivSec-dev/banking-apps-compat-report); it is not easy to filter for European banks, but the [incompatible](https://github.com/PrivSec-dev/banking-apps-compat-report/is...) ones are less than 10% of the total [reports](https://github.com/PrivSec-dev/banking-apps-compat-report/is...).

I don't know about LineageOS, but there is crowd-sourced list of banks that work with GrapheneOS: https://github.com/PrivSec-dev/banking-apps-compat-report More info here: https://grapheneos.org/usage#banking-apps My credit union wasn't on the list, but it works.

German bank Comdirect / Commerzbank did this as well, whitelisting GrapheneOS signing keys for their 2FA app. https://github.com/PrivSec-dev/banking-apps-compat-report/is...

Oh! Sorry, you described the current state of things so well I assumed you were close to the project. Here is the github repo where banking app compatibilities are tracked: https://github.com/PrivSec-dev/banking-apps-compat-report And it's rendered to a page here: https://privsec.dev/posts/android/banking-applications-compa...

At least in Switzerland banks can choose to not use Play Integrity, but they generally don't want to. Yuh, which once was owned by both Postfinance and Swissquote, works without Play Integrity. Support for GrapheneOS is confirmed - see https://github.com/PrivSec-dev/banking-apps-compat-report/is... The real issue is that most "legacy" banks have to comply with stupid regulations that force them to come up with these stupid solutions. Banks are lazy and find the quickest way to comply with said regulations - simply by enabling Google Play Integrity. About the whole US thingie - yes, that's true, and it's what happens if you get sanctioned. I'm pretty sure russians (and other people from sanctioned countries) have similar limitations elsewhere. In Switzerland US nationals have huge problems in opening accounts because of the whole bank secr

Can you say more about what specific things you tripped over with Starling, and which bank you moved to? Worried I'll find myself in the same boat. It does seem like Starling has gone out of their way twice to exempt GrapheneOS from their checks, but only after users complained: https://github.com/PrivSec-dev/banking-apps-compat-report/is...

GrapheneOS user here. Every single banking and financial app I use works. Both European ones and non-European. Some require changing per-app settings, but nothing crazy. There's a good chance that your banking app will work. https://github.com/PrivSec-dev/banking-apps-compat-report https://privsec.dev/posts/android/banking-applications-compa...

Here it is: https://privsec.dev/posts/android/banking-applications-compa... with its github backend https://github.com/PrivSec-dev/banking-apps-compat-report If you are in Europe, Curve recently enabled mobile payments without Google Pay, and that might solve the issue (but I haven't tried it myself). Some app that don't work because they require strong integrity are listed here: https://grapheneos.org/articles/attestation-compatibility-gu...

I checked a couple of reports relevant to me[1][2], and both explicitly mentions Play was installed and links to the Play store for the app. Can one still assume one can install and operate those apps without Google Play? [1]: https://github.com/PrivSec-dev/banking-apps-compat-report/is... [2]: https://github.com/PrivSec-dev/banking-apps-compat-report/is...