5 ms·
Is there E2EE in the actual RCS specification? Can there be, given that telcos are usually subject to lawful intercept laws? AIUI, what Google/Android does is
by throw0101a 3y ago
Is there E2EE in the actual RCS specification? Can there be, given that telcos are usually subject to lawful intercept laws?
AIUI, what Google/Android does is have their own extension, with the Content-Type of the message being "application/vnd.google.rcs.encrypted":
* https://www.gstatic.com/messages/papers/messages_e2ee.pdf https://www.gstatic.com/messages/papers/messages_e2ee.pdf
This is kind of like, with (E)SMTP/IMAP, having your own capability of "X-GOOG-ENCRYPT" if the standards-based "STARTTLS" was not around.
So while RCS gives many other improvement over SMS/MMS, encryption is not one of them.
(Personally I have an iPhone, but don't conect 'iMessage', and generally stick with SMS/MMS.)
- Andrex 3y agoThe MLS protocol proposed by Google provides a cross platform path to E2EE. https://thehackernews.com/2023/07/google-messages-getting-cross-platform.html?m=1 https://thehackernews.com/2023/07/google-messages-getting-cr...
- a2dam 3y agoThere isn't E2EE in the RCS spec, but there's in-transit TLS encryption
- jvolkman 3y agoSTARTTLS is client-to-server (or at least node-to-node). RCS node-to-node is already always encrypted. E2EE is like both sending and receiving parties agreeing to use PGP. The servers aren't involved with the details; they just move the opaque bytes.