2 ms·

I see a lot of confusing chatter about RCS (and maybe that’s the point). Does anyone actually have a good write up on E2E encryption and whether or not all mes

I see a lot of confusing chatter about RCS (and maybe that’s the point). Does anyone actually have a good write up on E2E encryption and whether or not all messages will actually go through google’s servers in plaintext? As in, not Google marketing. Seen a lot of chatter and it seems like it’s is complicated on both fronts. Only mildly worse (depending on the answer) than sending an SMS already but really makes me question the push for it in the first place

hot_gril 2y ago
I don't have a writeup, but RCS doesn't specify e2ee. Google has their own thing that doesn't work with other RCS clients (including Apple).
enragedcacti 2y ago
Its hard to avoid Google's marketing when the end-to-end implementation proprietary to their RCS app. This is their technical paper which confirms that it is end-to-end encrypted using the Signal protocol. The actual RCS spec has no support for E2E at this point. https://www.gstatic.com/messages/papers/messages_e2ee.pdf https://www.gstatic.com/messages/papers/messages_e2ee.pdf
aspenmayer 2y ago
Apparently Google acquired Jibe and offers it as a cloud solution to carrier OEMs to implement RCS. https://www.gsma.com/get-involved/gsma-membership/gsma_orgs/jibe-mobile-inc/ https://www.gsma.com/get-involved/gsma-membership/gsma_orgs/... https://techcrunch.com/2015/09/30/google-acquires-jibe-mobile-to-help-adopt-new-standard-for-carrier-messaging/ https://techcrunch.com/2015/09/30/google-acquires-jibe-mobil... https://android.googleblog.com/2015/09/committing-to-rcs-latest-standard-in.html https://android.googleblog.com/2015/09/committing-to-rcs-lat... https://jibe.google.com/jibe-platform/ https://jibe.google.com/jibe-platform/ https://www.sicurezzaegiustizia.com/wp-content/uploads/2020/12/messages_e2ee.pdf https://www.sicurezzaegiustizia.com/wp-content/uploads/2020/... > RCS uses a set of standard internet protocols like Session Initiation Protocol (SIP)[1] to establish a connection between two clients through a central messaging server. This connection is then used to exchange the messages using Message Session Relay Protocol (MSRP)[2]. In some RCS deployments this server is hosted by the carrier, and in other deployments the server is hosted by Jibe Mobile from Google. > In situations where the two clients are not on the same carrier network, they’re connected through multiple servers—one from each carrier. The connection between the RCS client app and the carrier’s messaging server is encrypted using Transport Layer Security (TLS). Server to server communications are also encrypted. How end-to-end encryption in Google Messages provides more security https://support.google.com/messages/answer/10262381 https://support.google.com/messages/answer/10262381 Google Messages end-to-end encryption technical paper https://www.gstatic.com/messages/papers/messages_e2ee.pdf https://www.gstatic.com/messages/papers/messages_e2ee.pdf Data security for RCS Business Messaging (RBM) https://developers.google.com/business-communications/rcs-business-messaging/support/data-security https://developers.google.com/business-communications/rcs-bu...

hot_gril 2y ago

I don't have a writeup, but RCS doesn't specify e2ee. Google has their own thing that doesn't work with other RCS clients (including Apple).

enragedcacti 2y ago

Its hard to avoid Google's marketing when the end-to-end implementation proprietary to their RCS app. This is their technical paper which confirms that it is end-to-end encrypted using the Signal protocol. The actual RCS spec has no support for E2E at this point. https://www.gstatic.com/messages/papers/messages_e2ee.pdf https://www.gstatic.com/messages/papers/messages_e2ee.pdf

aspenmayer 2y ago

Apparently Google acquired Jibe and offers it as a cloud solution to carrier OEMs to implement RCS. https://www.gsma.com/get-involved/gsma-membership/gsma_orgs/jibe-mobile-inc/ https://www.gsma.com/get-involved/gsma-membership/gsma_orgs/... https://techcrunch.com/2015/09/30/google-acquires-jibe-mobile-to-help-adopt-new-standard-for-carrier-messaging/ https://techcrunch.com/2015/09/30/google-acquires-jibe-mobil... https://android.googleblog.com/2015/09/committing-to-rcs-latest-standard-in.html https://android.googleblog.com/2015/09/committing-to-rcs-lat... https://jibe.google.com/jibe-platform/ https://jibe.google.com/jibe-platform/ https://www.sicurezzaegiustizia.com/wp-content/uploads/2020/12/messages_e2ee.pdf https://www.sicurezzaegiustizia.com/wp-content/uploads/2020/... > RCS uses a set of standard internet protocols like Session Initiation Protocol (SIP)[1] to establish a connection between two clients through a central messaging server. This connection is then used to exchange the messages using Message Session Relay Protocol (MSRP)[2]. In some RCS deployments this server is hosted by the carrier, and in other deployments the server is hosted by Jibe Mobile from Google. > In situations where the two clients are not on the same carrier network, they’re connected through multiple servers—one from each carrier. The connection between the RCS client app and the carrier’s messaging server is encrypted using Transport Layer Security (TLS). Server to server communications are also encrypted. How end-to-end encryption in Google Messages provides more security https://support.google.com/messages/answer/10262381 https://support.google.com/messages/answer/10262381 Google Messages end-to-end encryption technical paper https://www.gstatic.com/messages/papers/messages_e2ee.pdf https://www.gstatic.com/messages/papers/messages_e2ee.pdf Data security for RCS Business Messaging (RBM) https://developers.google.com/business-communications/rcs-business-messaging/support/data-security https://developers.google.com/business-communications/rcs-bu...