Earlier quoted context omitted.
Korean banking apps usually are disabled in rooted Android, probably because in rooted Android the integrity of the binary cannot be verified.
GrapheneOS is not rooted though. Are all of them doing SafetyNet checks too, not just root checks?
South Korea’s online security dead end
141–144 of 144 posts
Re: South Korea’s online security dead end
#142Earlier quoted context omitted.
There's a curious absence of Korean banking apps on this GrapheneOS compatibility list: https://privsec.dev/posts/android/banking-applications-compa... Does it mean none are usable on a modern clean Android? Or is there a total Samsung monoculture? Something else?
I live in Korea and run the latest GrapheneOS on Pixel 6. I have 6 different banking apps (Citi, IBK, Woori, etc.) installed and all of them work flawlessly. I also have a few government apps running and they work as well. There are definitely some apps that don't run on it (Donbaekjeon, Busan's local payment app being one) but overall they work.
Re: South Korea’s online security dead end
#143Earlier quoted context omitted.
There's a curious absence of Korean banking apps on this GrapheneOS compatibility list: https://privsec.dev/posts/android/banking-applications-compa... Does it mean none are usable on a modern clean Android? Or is there a total Samsung monoculture? Something else?
I live in Korea and run the latest GrapheneOS on Pixel 6. I have 6 different banking apps (Citi, IBK, Woori, etc.) installed and all of them work flawlessly. I also have a few government apps running and they work as well. There are definitely some apps that don't run on it (Donbaekjeon, Busan's local payment app being one) but overall they work.
It's great to hear that the compatibility situation isn't that bad in Korea. Have you considered submitting the apps to https://privsec.dev/posts/android/banking-applications-compa...? Otherwise people might make the same mistake as me (look at the list and assume it's impossible to use an alternate OS)
Re: South Korea’s online security dead end
#144Note this is written by Norman Feske, who later went on to develop Genode[1], and continues to be its main developer today.