Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

RCS is a net loss for privacy: it gives the carriers visibility into your social graph and doesn’t support end to end encryption. Google’s PR campaign tried to give the impression that RCS supports E2EE but it’s restricted to their proprietary client.


On top of that, rooted devices are denied access to it, which means Google is now gatekeeping a "carrier" service on top of that even more.


> rooted devices are denied access to it

By what? It's impossible for a process to know for sure if the system is rooted or not. A rooted system can present itself to a process to look like a non-rooted system if it's engineered well enough.

I'd bet that most of these apps probably just check if "su" returns a shell, in which case perhaps all that's needed is to modify the "su" executable to require "su --magic-phrase foobar" before it drops into a root shell, and returns "bash: su: not found" or whatever if called with no arguments.


>A rooted system can present itself to a process to look like a non-rooted system if it's engineered well enough.

That was true 20 years ago, but most smartphones these days have cryptograhically-verified boot chains and remote attestation of how the boot went.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: