[ravenstine]

This is rubbish. I'm running GrapheneOS and have left my bootloader unlocked, and there's no app that has refused to work. The only caveat is some of them need Google Play services. No, I am not rooted, but my last phone was rooted and there might have been one or two apps out of dozens that wouldn't work with root even with Magisk trying to hide the root status. Using a custom ROM is easily one of the beat choices I have made.

[nebulous1]

Do you use a banking app? Last I read depending on the type of check used some apps can still be problematic.

[iforgotpassword]

So I guess next thing we need is someone sueing the fucking banks that do that. Mine luckily doesn't because I explicitly use an old phone with LineageOS, the banking app, and nothing else on it for online banking. It's arguably way more secure than using your main phone with a bazillion other Apps installed and online at all times.

[eganist]

How would that stick? You can just sign into the bank via your web browser in the case of a nonfunctional app. The apps just give you added security assurances beyond using the web.

"The app can't function in a low security environment, but complainant is free to use the web client in such event." case dismissed

(obviously an oversimplification, but the point stands)

[erinnh]

This is definitely not the case everywhere.

Where I live the app is 100% needed because it’s the „second factor“ in the login process.

[The_Colonel]

There has to be a fallback like SMS and/or automated call.

[akvadrako]

For my banks the only fallback is a hardware device that you put your card into. Before the app you had to carry this everywhere when traveling to do online banking.

[Too]

SMS is magnitudes less secure than the Secure Enclave in my phone.

Fallback should never be the weakest link in a security chain. Especially not in something as high stakes as your banking login.

I can’t remember how I got my first bank token in my phone. Probably by physically showing up in the bank office with my id.

[eganist]

Curious, can you name this institution that only allows the app to be used as the second factor without fallbacks?

[iforgotpassword]

In Germany: all of them.

Well, some offer a hardware device for like 25€ that can do the same thing, but then if you have an account with multiple banks, you need multiple of these devices.

[oarsinsync]

There are app-only banks too. Some of them provide a web interface, but it depends on the app to sign you into the web interface (similar to the way whatsapp requires you to use the app to sign into whatsapp web).

What happens when you primary bank has been one of these app-only banks for the last 5 years, and you decide to make a technology change to your phone, and can now no longer get into your banking app?

[realusername]

When you reject GrapheneOS, the most secure mobile OS on the planet but accept a no-name chinese ROM I feel like that you can't invoke security reasons anymore.

[Too]

Signing transactions usually take you back to the 2FA app here, where the amount and receiver is repeated.

Even if someone hijacks my computers web browser, the worst they can do is see my statements, any attempt to transfer out will pop up a prompt in the phone.

[iforgotpassword]

The app is for 2fa.

[didntcheck]

A lot of this actually seems to have come from recent regulatory pressure for 2FA (which I support in principle, don't get me wrong). I don't even think most of them have given much thought to rooted phones, rather they're just cargo culting Industry Standard Best Practices and turning all the device verification options to max. Luckily, most of them realize they still have customers without a compliant smartphone, or one at all, and offer a fallback, which is almost always SMS...

Though you get those newer "app only" banks. I've never used any since I see that as a major downside, not a selling point, so idk whether they tolerate root. Even with traditional banks, I've come across a few features which can only be accessed via the phone app - in this case likely due to the belief that "web? Everyone just uses apps!" rather than security

[udev4096]

It's far from secure. You are using an outdated phone, which hasn't received any kind of firmware or vendor security patches in a while. And as far as I remember, LineageOS doesn't support relocking the bootloader which further reduces the overall security of your phone

[iforgotpassword]

What's the attack vector? There is nothing else installed on this phone, and I only turn it on when the banking website asks me to confirm the login via their app. So it's connected to my wifi for like 5 minutes.

Meanwhile my main phone is always on the mobile network, using a proprietary modem that's running ridiculously complex firmware that does edge, lte, 5g, VoIP, has its own tcp/ip stack and a dozen other super complex protocols, is closed source, gets no security reviews and is exposed to at least my mobile provider at all times. And that's just the modem. Don't let me get started with all the value-add software the phone vendor loaded the device up with. Some of which is running with elevated privileges. You seriously think this is more secure?

[jiminymcmoogley]

For UK banks on my Graphened Pixel 6a I can use the apps for HSBC, First Direct, Barclays, NatWest, RBS, Co-Operative Bank and Metro Bank with no issues, and have only had trouble with the Lloyds Bank app as of an update from maybe 2-3 months ago which throws an error saying they've detected I'm using a jailbroken/rooted device

[White_Wolf]

I get a message that the device is not secure but I can still make transfers and such from the banking app on a rooted OP9Pro. Never tried to use NFC payments though.

[doublerabbit]

Try using Monzo or Sterling.

Both will nail you to the ground.

[baby_souffle]

> Do you use a banking app? Last I read depending on the type of check used some apps can still be problematic.

It's important to distinguish between banking app and payment app. If you just want to check your account balance or find an ATM, the banking app will probably not mind that you're on a device that can't pass integrity checks.

If you want to use your phone's NFC to pay for coffee, though, you're going to have a bad time.

[didntcheck]

Also many "corporate" things, usually depending on your org's policy. E.g. I can't run OpsGenie (it may actually be the Microsoft SSO step failing, I'm not entirely sure, but the error definitely mentions my device not meeting security policies)

[Xfx7028]

I use N26, Revolut, ING, and others. No issues, I just add the apps I need to the magisk hide list. I also use NFC payments. Only Google wallet does not work.

[ravenstine]

Yes. Wells Fargo, Discover, Alliant CU, Venmo, Paypal, and M1 Finance all work.

[zerreh50]

Same with McDonald's, interestingly enough

[vidarh]

Yeah, my bank app both did not work with rooted phones, last I checked, and they also appear to whitelist phone models or something - at one point I had an uncommon mid-range Chinese phone and I had to contact support to have them approve my phone.

[Fire-Dragon-DoL]

What are the downsides with GrapheneOS? I had a few problems with root (Netflix and banking apps) but would love my privacy. My main reason for root is the firewall to block outgoing connections from apps that are not supposed to do it

[0xcde4c3db]

It's really a downside of the Google app ecosystem and not GrapheneOS per se, but apps requiring higher levels of integrity per Google attestation (Play Integrity/SafetyNet) generally won't work. Intentionally breaking apps on "untrusted" configurations is basically the point of that feature, and GrapheneOS does provide the relevant services, but would need to be specifically enabled by the app developer.

[Fire-Dragon-DoL]

So Netflix and such DO NOT work on phone? That's really frustrating

[udev4096]

Firewall wouldn't be necessary with GrapheneOS. There's a network toggle which you can use to completely cut off internet access for an app. As for the downsides, I would say close to zero. It feels just like a stock OS, without any kind of bloatware and a lot more secure

[ThePowerOfFuet]

GrapheneOS is not rooted, so you won't have those issues.

GrapheneOS also gives you a Network permission per-app; if you uncheck it, the app has no connectivity, period.

Highly recommended.

[Fire-Dragon-DoL]

Based on the other comment thread, it seems like Play Integrity and SafetyNet do not succeed and as such, can't really use Netflix, is that correct?

[ThePowerOfFuet]

Apparently Google is playing games in the Play Store, but if you can get it installed then it runs fine:

https://discuss.grapheneos.org/d/696-issues-with-netflix-app

I just verified that I could download it just fine using Aurora Store, and I don't have Google anything installed.

[switch007]

No NFC payments with Google wallet.

You can get unlucky with your bank app but someone maintains a wiki of compatible banking apps

Android auto works OK.

[DEADMINCE]

One big downside is being limited to Pixel phones, without good reason.

[ThePowerOfFuet]

You should not leave your bootloader unlocked if you care about the security of your device and data.

Unfortunately, locking (and unlocking) it wipes user data, so it should be relocked right after installation of GrapheneOS.

[didntcheck]

Don't most phones only wipe on unlock?

Also can Graphene still update if the bootloader is locked?

[ThePowerOfFuet]

The Pixels wipe on both lock and unlock.

Yes, it can still update just fine. It installs its own certificate at install time and all updates are signed with it.

[ravenstine]

I acknowledge that.

[collegeburner]

what? safetynet is absolutely a pain in the ass. i think there are some xposed and magisk modules or whatever that can work around it but that's a cat-and-mouse thing and can break. lot of bank and financial apps, lot of stuff with DRM will break.

[63stack]

No, parent is 100% correct. Unlocking your bootloader trips SafetyNet.

[udev4096]

GrapheneOS is not a ROM. It's an OS.

[jstanley]

What's the difference?