4 ms·
> end-to-end encryption which is something RCS doesn’t do according to this article The article is not quite correct. The base RCS standard does not include E
by kelnos 5y ago
> end-to-end encryption which is something RCS doesn’t do according to this article
The article is not quite correct. The base RCS standard does not include E2E encryption, but at least Google's implementation includes it as an extension. Not an ideal situation -- IMO it should be a required-to-implement part of the base -- but it's definitely there for those of us using Google's infra, at least.
- r00fus 5y agoHow does E2EE work if one portion of the chain is not encrypted? Would it only work if both you and your message partner installed the extension? Part of the elegance of iMessage is that E2EE isn't optional.
- sudosysgen 5y agoE2EE is optional, and disabled by default. Out of the box, your iPhone will store your messages in cleartext on Apple servers every time it backs up.
- r00fus 5y agoThis is a twisted way of seeing it. E2EE is mandatory in Messages. Backup is optional - my phone has never seen an iCloud backup (all local backups).
- sudosysgen 5y agoNo, it's not. By default, iMessage messages are stored in cleartext on Apple servers. You need to use an option, to disable iCloud backups, so that this isn't th case. So the messages are only E2EE if you take care to change the options so that they are, otherwise they are not. I don't think I'm twisting it. Pragmatically, unless you fiddle with the options, iMessage won't give you end to end encryption. So I think it's fair to call it optional.