this post was submitted on 16 Aug 2023
95 points (100.0% liked)
Technology
37712 readers
416 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Google has managed this years ago, but it's optional. There was a fairly short timeframe when most phone makers enforced it, but now most allow power users to disable the security and root their phones. But usually they will disable some security-sensitive features like Samsung Knox. And many security-sensitive apps like banking apps will not let you run them anymore (if yours does, great for you, but that also means your bank's security is shit, just FYI).
A banking app allowing itself to run on rooted devices isn't a security issue.
Depends on your level of security consciousness. If you're relying on security identifiers or apis that need an "intact" system, it certainly can be a security issue if you can't rely of those.
That being said, it's not exactly a plausible risk for most people or apps.
That's right. And if there is, the issue is the bank, not your phone. Rule number 1 in security is never trust the client.