search

GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
352 stars 19 forks source link

Optional toggle to allow Play Services to access certain hardware identifiers to properly enable RCS support #4085

Open duck09 opened 1 week ago

duck09 commented 1 week ago

There is a forum thread with a staggering 435 posts spanning over 2 years discussing how to get RCS working on GrapheneOS. People resort to hacky workarounds which are not reliable and usually disconnect RCS after a while such as using shizuku which is not recommended by the GrapheneOS team.

An optional toggle that allows Play Services to access hardware identifiers will allow users to properly enable RCS without resorting to any workarounds but with a privacy cost.

duck09 commented 1 week ago

I wouldn't mention the steps here publicly so people do not get any ideas an follow them, effectively reducing their security. A similar comment talking about this was removed due to this reason. It would be best if you deleted your comment.

rei-zero246 commented 1 week ago

Is the purpose of this issue to raise awareness, or for a solution?

duck09 commented 1 week ago

Is the purpose of this issue to raise awareness, or for a solution?

It's a feature request for the solution (which is listed in the title).

ZLima12 commented 4 hours ago

It should be noted that Google Messages is only one implementation of RCS (although admittedly the most used one). Some carriers have offered their own RCS services, which I believe is more in-line with what the GSMA intended. Some have already begun to phase these out in favor of Google's implementation, but perhaps this will change now that Apple is adopting the standard. Either way, being able to use RCS without Google Play would be good for the users who don't wish to install that.