Apple Tests End-to-End Encrypted RCS Messaging in iOS 26.4 Developer Beta
Source: The Hacker News
Apple released a new developer beta of iOS and iPadOS (26.4) that adds end‑to‑end encryption (E2EE) for Rich Communications Services (RCS) messages.
RCS End‑to‑End Encryption
- The feature is currently available for testing in iOS and iPadOS 26.4 Beta and is expected to roll out to iOS, iPadOS, macOS, and watchOS in a future update.
- Apple notes that “End‑to‑end encryption is in beta and is not available for all devices or carriers.” Conversations labeled as encrypted are protected so that messages cannot be read while in transit between devices.
- Encryption is limited to conversations between Apple devices; it does not extend to other platforms such as Android.
The test arrives about a year after the GSM Association (GSMA) formally announced support for E2EE in RCS. Implementing E2EE for RCS will require Apple to adopt the RCS Universal Profile 3.0, which is built on the Messaging Layer Security (MLS) protocol.
Memory Integrity Enforcement (MIE)
The beta also introduces a new option for applications to opt‑in to full Memory Integrity Enforcement for enhanced memory‑safety protection. Previously, apps were limited to “Soft Mode.”
MIE, unveiled by Apple last September, provides “always‑on memory safety protection” across critical attack surfaces such as the kernel and over 70 user‑land processes, with no performance overhead.
Stolen Device Protection
According to MacRumors, iOS 26.4 is expected to enable Stolen Device Protection by default for all iPhone users. The feature adds:
- A requirement for Face ID or Touch ID authentication when performing sensitive actions (e.g., accessing stored passwords or credit cards) while the device is away from familiar locations (home, work, etc.).
- A one‑hour delay before allowing Apple Account password changes, giving users time to mark the device as lost if it is stolen.
References