Skip Navigation

Revolut, McDonald's, and Authy have banned the use of GrapheneOS.

grapheneos.org

GrapheneOS attestation compatibility guide

cross-posted from: https://slrpnk.net/post/15995282

Real unfortunate news for GrapheneOS users as Revolut has decided to ban the use of 'non-google' approved OSes. This is currently being posted about and updated by GrahpeneOS over at Bluesky for those who want to follow it more closely.

Edit: had to change the title, originally it said Uber too but I cannot find back to the source of ether that's true or not..

331 comments
  • Odd timing considering I've banned McDonalds, Revolut and Authy from my phone.

  • Lol I spent a week going back and forth with Revolut support in august. I could sign into the app but it would always ask me for a "selfie" verification and every time support would say its a super dark selfie.

    Eventually I decided to try a stock ROM and it just worked and I realised what was happening so I transferred all of my money out and deleted my account.

    Most local banks here are terrible at making apps, some even require a separate device that looks like a calculator to use online banking, so hopefully they wont follow suit anytime soon

    • require a separate device that looks like a calculator to use online banking

      To be fair this actually provides a very high level of security? At least in my experience with AIB (in Ireland) you needed to enter the amount of the transactions and some other core details (maybe part of the recipient's account number? can't quite recall). Then you entered your PIN. This signed the transaction which provides very strong verification that you (via the PIN) authorize the specific transaction via a trusted device that is very unlikely to be compromised (unless you give someone physical access to it).

      It is obviously quite inconvenient. But provides a huge level of security. Unlike this Safety Net crap which is currently quite easy to bypass.

      • Those little boxes are just a bit of hardware to let the smartchip on the smartcard do what's called challenge-response authentication (in simple terms: get big long number, encode it with the key inside the smartchip, send encoded number out).

        (Note that there are variants of the process were things like the amount of a transfer is added by the user to the input "big long number").

        That mechanism is the safest authentication method of all because the authentication key inside the smartchip in the bank card never leaves it and even the user PIN never gets provided to anything but that smartchip.

        That means it can't be eavesdropped over the network, nor can it be captured in the user's PC (for example by a keylogger), so even people who execute files received on their e-mails or install any random software from the Internet on their PCs are safe from having their bank account authentication data captured by an attacker.

        The far more common two-way-authentication edit: two-channel-authentication, aka two-factor-autentication (log in with a password, then get a number via SMS and enter it on the website to finalize authentication), whilst more secure that just username+password isn't anywhere as safe as the method described above since GSM has security weaknesses and there are ways to redirected SMS messages to other devices.

        (Source: amongst other things I worked in Smart Card Issuance software some years ago).

        It's funny that the original poster of this thread actually refuses to work with some banks because of them having the best and most secure bank access authentication in the industry, as it's slightly inconvenient. Just another example of how, as it's said in that domain, "users are the weakest link in IT Security".

      • In Germany they're called TAN generators if you want to learn more

    • Crazy how the response is to completely gaslight you about what the real issue is

      • That's pretty typical when its a low level machine learning algorithm that flagged the account. Usually the support rep legitimately doesn't know, and you'll get stuck in an infinite loop

  • Banks seem to be hit or miss, happy that mine works. Would rather switch Banks than use a stock Rom, though.

    All the Uber stuff works in Browser, both eats and their fake taxi stuff.

    Not having a subtle reminder to eat at McDonald's is probably better for you.

    Honestly, if your app could be a website, and includes services not on your website, fuck you, I'm gonna go to the competition.

  • Anyone tried waydroid or android in an emulator for these type of apps ?

    • Oh yeah that's an insta-ban. And even the waydroid app devs say their security is atrocious and you shouldn't use it for banking.

  • I swear I am so close to jumping into the void of mainline linux on phones.

    The only main issue is device drivers, but I would be fine happily extracting them from android or making new ones. Modern Android is a complete full stack POS.

  • I use McDonalds App all the time on GOS this only affect you if you use Google Pay when checking out to my knowledge.

331 comments