this post was submitted on 10 Dec 2023
250 points (96.3% liked)

Android

17682 readers
112 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: [email protected]


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 11 months ago

It's not natively supported by the base RCS standard, in the section at the end of the paper in the section titled "Third Party RCS Clients" Google explains that they've built the e2ee their Messages app themselves, (on top of standard RCS).

A developer has to use Google's implementation specifically in order to send and recieve e2ee messages to Google's Messages app (and Samsung Messages who also implemented this recently)

Although the e2ee implementation is using the Signal protocol under the hood, it's for message content only - this is what is transmitted in cleartext (taken from the paper)

  • Phone numbers of senders and recipients
  • Timestamps of the messages
  • IP addresses or other connection information
  • Sender and recipient's mobile carriers
  • SIP, MSRP, or CPIM headers, such as User-Agent strings which may contain device manufacturers and models
  • Whether the message has an attachment
  • The URL on content server where the attachment is stored
  • Approximated size of messages, or exact size of attachments

Without using this implementation of the Signal protocol on top of RCS, the message will deliver to the contact's phone, but shows up as unencrypted garbled text

That is a very useful resource though, never knew there was a paper available on the implementation. Saving 😁