E2EE is not part of the standard and only exists as a proprietary Google extension, using Google’s servers. Implying that implementing RCS would get everyone cross-platform E2EE is misinformation.
And why should apple (or anyone for that matter) be forced to use googles proprietary code for an “open standard”?
Also,
There is, naturally, a wrinkle here. The RCS standard still doesn’t support end-to-end encryption. Apple, which has offered encrypted messaging for over a decade, is kind of a stickler about security. Apple says it won’t be supporting any proprietary extensions that seek to add encryption on top of RCS and hopes, instead, to work with the GSM Association to add encryption to the standard.
Apple offers first party E2EE messaging for their clients, via iMessage.
As part of China’s certification requirements, Apple has been tasked to support RCS, which, per the spec, does not have E2EE feature.
I’ll say this again: RCS does not support E2EE.
If that’s not registering: RCS does not support E2EE.
Come to the think of it, it would actually be surprising if China is mandating an E2EE capable implementation, but I digress.
In order to comply with this requirement, Apple implemented RCS per the specs of RCS. Again, RCS does not support E2EE. There is no specification of RCS that supports E2EE at this time.
Google runs a proprietary system that they’ve built based off of RCS, but is not RCS. This proprietary protocol, which is not RCS, has custom extensions of their own to offer E2EE. Apple is under zero obligation to implement against this, because this is not RCS. In fact, as demonstrated, even other Android systems don’t do this. They use the carrier RCS, which while fragmented and incomplete, consistently does not have E2EE, because, again, RCS does not support E2EE.
There are plenty of cross platform E2EE solutions available: Matrix, Signal, and WhatsApp, are a few major players that popped to mind. I’m sure there are plenty of others that I didn’t call out. They are cross platform which means they already exist on both iOS and Android platforms.
Neither Apple nor Google have any reason to implement those protocols, as, again, they already exist on platform.
How is Apple not implementing Google’s proprietary extension malicious compliance as you called it?
E2EE is not part of the standard and only exists as a proprietary Google extension, using Google’s servers. Implying that implementing RCS would get everyone cross-platform E2EE is misinformation.
Yes, that is the point I was making, thank you for elaborating.
Correct again, thanks.
And why should apple (or anyone for that matter) be forced to use googles proprietary code for an “open standard”?
Also,
https://www.techradar.com/phones/iphone/breaking-apple-will-support-rcs-in-2024
They shouldn’t.
Well then why did you describe them not doing that as malicious compliance?
Because there are 5000 different open protocols they could have chosen from.
To support E2EE in RCS?
Correct
Apple offers first party E2EE messaging for their clients, via iMessage.
As part of China’s certification requirements, Apple has been tasked to support RCS, which, per the spec, does not have E2EE feature.
I’ll say this again: RCS does not support E2EE.
If that’s not registering: RCS does not support E2EE.
Come to the think of it, it would actually be surprising if China is mandating an E2EE capable implementation, but I digress.
In order to comply with this requirement, Apple implemented RCS per the specs of RCS. Again, RCS does not support E2EE. There is no specification of RCS that supports E2EE at this time.
Google runs a proprietary system that they’ve built based off of RCS, but is not RCS. This proprietary protocol, which is not RCS, has custom extensions of their own to offer E2EE. Apple is under zero obligation to implement against this, because this is not RCS. In fact, as demonstrated, even other Android systems don’t do this. They use the carrier RCS, which while fragmented and incomplete, consistently does not have E2EE, because, again, RCS does not support E2EE.
There are plenty of cross platform E2EE solutions available: Matrix, Signal, and WhatsApp, are a few major players that popped to mind. I’m sure there are plenty of others that I didn’t call out. They are cross platform which means they already exist on both iOS and Android platforms.
Neither Apple nor Google have any reason to implement those protocols, as, again, they already exist on platform.
How is Apple not implementing Google’s proprietary extension malicious compliance as you called it?