Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

NobodyElse

@NobodyElse@sh.itjust.works

This profile is from a federated server and may be incomplete. Browse more on the original instance.

NobodyElse ,

Had to look that up too. My immediate reaction was wondering if Thalasin works for them too?

https://m.youtube.com/watch?v=Td2x8s9GZlo

NobodyElse ,

E2EE is not part of the standard and only exists as a proprietary Google extension, using Google’s servers. Implying that implementing RCS would get everyone cross-platform E2EE is misinformation.

NobodyElse ,

So is this going to be standard RCS, which has no encryption and the telcos need to support, or the Googlified version that does E2E encryption but requires storing keys on Google’s servers?

RCS has interoperability issues itself and Google hasn’t been making the situation better.

NobodyElse ,

On my phone, so links may come later.
It’s hard to find solid documentation on it, since their encryption extension is proprietary, but it’s been referenced as being based on the Signal Protocol. The Signal Protocol, or every implementation of it that I’ve seen, uses a central “trusted” repository of public keys to tell message originators query to encrypt the message to. For Signal, and I assume Google RCS, that central repository is Google. The protocol doesn’t allow for federation, so any system that is interoperable with Google RCS will rely on Google as the trusted authority.

The private key part I’m much less sure of, since both the Signal and Google RCS clients are closed source. Signal makes you jump through hoops to add a new client, involving one of your currently installed clients. This suggests that Signal isn’t in possession of your private keys. On the other hand, all you need to set up a new Google client is your account password. This suggests that either your keys are held by Google (perhaps encrypted by your account password) or that new keys can be added without needing explicit involvement from current keys.

Of course this is all speculation because the implementations aren’t available for inspection.

NobodyElse ,

RCS, as adopted by GSMA , is zero encryption text messaging. RCS with encryption is a proprietary Google product and relies on Google servers.

NobodyElse ,

Yes. I’m a man of few words.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • incremental_games
  • meta
  • All magazines
    •