0

Seems Google Messages May Finally Be Adding End-to-End Encryption for RCS.

Messages suggests it may be moving closer to having end-to-end encryption for RCS, which is according to APKMirror. Rich Communication Services, or RCS, is the successor to SMS messaging and does what most other texting services do, but without the end-to-end encryption that apps like Signal and iMessage have. Its widespread adoption has been a bit of a mess, but the major US cellular carriers announced late last year that they would offer RCS in 2020.

Well Google first unveiled RCS chat as Android’s primary texting platform in 2018, actually rolling out it out first to users in the United States.

An internal build of Google Messages V.6.2 has several lines of code that offer clues to possible future features for the app, including 12 new strings that refer to encryption, according to 9to5 Google’s analysis. There isn’t enough information available to determine whether the sender and recipient of texts in Messages would need to be using the app for the end-to-end encryption to be in effect. According to the code updates they suggest a setting that might allow users to decide whether to grant permission to other Android apps that have access to messages to see encrypted messages as well.

There is no way to know if or when Google will ever ship the end-to-end encryption feature. But the company has said previously that it was working on it, so it seems likely to happen.

As all of this is only just beginning to appear in a “dog-food” build of Google Messages, we still have a bit of waiting to do before end-to-end encryption arrives for RCS. That said, it’s clear Google wants RCS to be a legitimate competitor to iMessage, matching it both in features like message reactions for the everyday user and and ones like encryption for the more security conscious. Well I hope you are eager to meet the new feature RCS as i am.

SHARE THIS POST

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: