Google has been trying for years to install RCS for RCS, rich in cross-platform SMS successor. In the end, it seemed that it could be done: Apple has finally served for its ISSAGE app since iOS 18.2, which is the standard messenger on the iPhone. Problem: Currently, shipping between equipment – ie Android and iPhone – is still unprotected, sometimes as unsafe as SMS. It should only be replaced with iOS 19 – first in autumn 2025.
However, RCS has been long encrypted between Google devices if you use Android standard messenger. But now GSM Association (GSMA), Association of Mobile Phone Network Operators, want to remedy: The new RCS Universal Profile 3.0 promises to apply encryption in the communication service in completeness, despite that it is a stock Android, a customized Android or iPhone, until the profile is supported.
Hopefully active by default
GSMA-RCS Universal Profiles are 3.0 specifications Officially released“The biggest step with this latest version is that it includes requirements and user experiences for end-to-end encryption of RCS messages”; Write the organization which is aware of the importance. “This includes not only in encryption and control of users, but also like side effects such as client-side spam detection and its treatment requirement.”
Unlike IMESSAGE forcing encryption, RCS encryption will be discontinued, even if it should be actively switching, as already known from other messengers. This will be ugly because despite the technical ability to secure it, many users keep using its use unique. It is also possible that safety in a group chat is downgrated from encrypted to unknowing when a member invites a person without active encryption. The text-typing indicator, ie indication that a user is typing something, is not encrypted at all.
Mls instead of TLS and IPSEC
The encryption standard used by RCS Universal Profile 3.0 is called Messaging layer securityMls for short. Among other things, it allows the review of the integrity of a message, further to the sec and is already used by Google for its in-house RCS encryption. Similar to the web encryption protocol TLS, the idea is a similar standard. However, Apple will only use MLS for communication with RCS contradictions, the group continues to cook its own soup for internal impersage encryption, for which the last time also last time Add pq3 Needed
Working on RCS Universal Profile 3.0 was already Started in 2022, a first definition document was published at that time“User network interface transactions should always be encrypted to prevent the user’s personal communication from listening to various access and transit network,” it says as a target. At that time, however, they wanted to rely on TLS and IPSEC. The British Government, which has tried to force Apple in a back door just in iCloud, meanwhile RCS encryption Probably not at all,
With the implementation of RCS encryption, one day the end of SMS may be pending at the end-or at least their uncertain use. Text messages are generally uninterrupted, for a long time they have been recommended to use for two-factor authentication methods (2FA), even though Apple still uses self-technology as a decline. It is not clear that SIM card kidnapping with encrypted RCS messages will still be possible, as you know from SMS: “kidnappers” attackers attacked the victim’s telephone number through mobile phone provider (via (e-) SIM Exchange) and then 2 FA code can be sent. Meanwhile, RCS Universal Profiles 3.0 promises other interesting innovations. This includes the possibility of reaping the messages sent and reversing shipping. Tapback is also planned with any emoji and paintings.
(BSC)
