End-to-end encryption for RCS with iOS 26.5: How to
After extensive internal testing, the public can now communicate more securely with RCS on iPhone. However, the technology is still in beta.
Symbol for encrypted RCS chat on an iPhone: Look closely.
(Image: Apple)
Arguably the most important innovation in iOS 26.5 (as well as iPadOS 26.5, macOS 26.5, and watchOS 26.5) is the ability for the public on Apple devices to encrypt RCS messages for the first time. Following tests in iOS 26.4 and Co., Apple is now beginning an official beta phase for this. This was also officially confirmed by Google on Monday evening. These are the possibilities, and here's where it still falters.
A Matter of the Network
First, one should look at which carrier actually supports end-to-end encryption (E2EE) for Rich Communication Services. Apple has published a support document for this. In Europe, these are 1&1, O2, and Telekom in Germany.
Videos by heise
Vodafone is currently not participating; the reason is unclear. Important: The other party must either be an iPhone with current software or an Android device with the “latest version of Google Messages,” as Apple announces. The company also shows a bit of defiance, continuing to write that its proprietary iMessage remains “the best way to communicate between Apple devices.” After all, end-to-end encryption has always been used there.
Mini-Icon Indicates Encryption
Furthermore, it is important to check if E2EE is running at all. Apple indicates this with a small lock (see image). Commendable: All E2EE-capable RCS communication is automatically encrypted; even already started conversations should be automatically switched to it, according to Apple, “after some time” without further details.
Google itself writes in its official blog that RCS with E2EE is “immediately” available to users of Google Messages. They have undertaken a “cross-industry effort” with Apple to make RCS, which is considered the successor to SMS, more secure and private. The latest version of Google Messages is, as mentioned, mandatory. Here too, new chats should use E2EE immediately, while older ones will have it activated gradually.
For E2EE for RCS on iOS, the RCS Universal Profile 3.0 is used, which in turn employs the Messaging Layer Security protocol. RCS Universal Profile 3.0 can, among other things, also edit and delete messages retroactively, has Tapback support, and inline replies. However, not all features are implemented on iOS. What beta means in the context of E2EE for RCS has not been revealed by Google and Apple. However, it is possible that the service is less reliable – at least for now.
Empfohlener redaktioneller Inhalt
Mit Ihrer Zustimmung wird hier ein externer Preisvergleich (heise Preisvergleich) geladen.
Ich bin damit einverstanden, dass mir externe Inhalte angezeigt werden. Damit können personenbezogene Daten an Drittplattformen (heise Preisvergleich) übermittelt werden. Mehr dazu in unserer Datenschutzerklärung.
(bsc)
