Pressure grows on Apple to open up iMessage::Samsung has joined Google’s campaign to force Apple to make iMessage RCS-compatible—but European regulators are more likely to get that job done.

  • fartsparkles@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I’ve just been reading the RCS Universal Profile Service Definition Document and it does stipulate encryption should be used but it is hardly defined how encryption should be implemented nor does it set an interoperable standard for it. I like RCS even less now.

    Methods for encryption, client verification, user authentication and access authorisation are applied by the client and the network on a per interface and protocol basis.

    So basically RCS is happy for there to be interoperability with regards to encryption, almost forcing interoperable implementations to forgo encryption so that different implementations can communicate.

    Signal protocol is far far far better a standard than this lazy “service definition”.

    • phillaholic@lemm.ee
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      Yea, the standard is great for a decade+ ago when it came out, but I’d never trust it as is over other things like Signal or even iMessage. Google’s RCS implementation is as trustworthy as anything else Google makes. They don’t even support it across all their products last I heard. It’s a joke.