PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-11-08 16:01:34 -05:00
Code
f408929d59
privsec.dev/content/posts/android/Banking Applications compatibility with GrapheneOS.md
akc3n cc3b44f17c
Add banking report 293 296 298 (#160) 
* Update gist urls for non-github user banking app reports

* Fixed url for metro banking app.

* Add banking report 293, 296 and 298
2023-09-26 23:15:58 -07:00

48 KiB
Raw Blame History

title date tags author
Banking Applications Compatibility with GrapheneOS 2022-01-26
Applications
Android
Banking
Compatibility
GrapheneOS
akc3n, Tommy

A maintained compatibility list of working international banking apps that are tested, submitted, reviewed and published below.

View list | Submit report | Update report

Introduction

This is a crowd-sourced project dataset for GrapheneOS's users that are on currently supported devices.

First time visitors here should read the official usage guide on banking apps for detailed information explaining how banking apps work on GrapheneOS.

Important: SafetyNet is being replaced by Play Integrity API and may cause your banking app to suddenly stop working after an update.

If your newly installed banking app aborts at first launch or suddenly stops working after your app updates, then you should try one of these possible solutions to resolve the compatibiity issue.

International banking apps

Argentina

Australia

Austria

Belgium

Brazil

Canada

Czech Republic

Denmark

Ecuador

Finland

France

Germany

Ghana

Hungary

India

Ireland

Israel

Italy

Kazakhstan

Luxembourg

Lithuania

Malaysia

Netherlands

Norway

Poland

Portugal

Romania

Russia

Serbia

Singapore

Slovenia

South Korea

Spain

Sweden

Switzerland

Taiwan

Thailand

Ukraine

United Arab Emirates

United Kingdom

United States

Vietnam

Prerequisites

This section covers how to submit or update a banking app report.

Submit a new app report

There are several methods for GrapheneOS users to contribute their banking app report:

Method Description Action
GitHub Fill out form on issue-tracker using your GitHub account SUBMIT REPORT
Non-GitHub View gist → Raw → Save template markdown file to fill out. Gist
Curl Terminal → curl -O → paste copied url (gist form .md template) ⟶ Copy link address
Google Form N/A at the moment N/A
OhMyForm N/A at the moment, need to test N/A

Alternatively, curl and pipe the output directly into vi/vim/neovim for editing:

curl https://gist.githubusercontent.com/akc3n/e845078ddbbb28ada0dd055c51ec45af/raw/dad087a1bafb838555423f41517e1998b710d1b4/banking-app-report-issue-form.md\?T | nvim -

Update status of app report

Please do not open a new issue to update the status of a banking app report!

Use the issue tracker to search for the banking app name listed above in the International banking apps section and add a comment to that report.

If you are a non-github user and have tried every combination suggested for possible solutions without being unable to resolving your specific banking app compatibiliity issue, then contact me afterwards please.

Note

GrapheneOS has a detailed guide for app developers on how to support GrapheneOS with the hardware attestation API. Direct use of the hardware attestation API provides much higher assurance than using SafetyNet so these apps have nothing to lose by using a more meaningful API and supporting a more secure OS.

GrapheneOS users are strongly encouraged to share this documentation with app developers enforcing only being able to use the stock OS. Send an email to the developers and leave a review of the app with a link to this information. Share it with other users and create pressure to support GrapheneOS rather than locking users into the stock OS without a valid security reason. GrapheneOS not only upholds the app security model but substantially reinforces it, so it cannot be justified with reasoning based on security, anti-fraud, etc.