4 ms·
E2EE is a true/false label. Either it is, or it ain’t. It is not mathematically possible to selectively break E2EE. If it’s broken, it’s not E2EE.
by kstrauser 3y ago
E2EE is a true/false label. Either it is, or it ain’t.
It is not mathematically possible to selectively break E2EE. If it’s broken, it’s not E2EE.
- deleted 3y ago[deleted]
- hot_gril 3y agoThere are stronger and weaker forms of it, though. Apple holds the keys to the identity (public key) exchange in iMessage. You're still trusting Apple not to mitm your conversations, but at least they wouldn't be able to do this retroactively. Other E2EE messaging apps at least have a way to verify each others' pubkeys, but it's not required and very few people do it.
- kstrauser 3y agoApple previously announced their "iMessage Contact Key Verification" (https://www.apple.com/newsroom/2022/12/apple-advances-user-security-with-powerful-new-data-protections/ https://www.apple.com/newsroom/2022/12/apple-advances-user-s...). Rumors are that it's coming in iOS 16.6 which may drop any time now.
- hot_gril 3y agoThat's cool. The article mentions a more common attack I forgot about, someone managing to add a new device to someone's account and get messages on there.
- InsomniacL 3y agoThe device manufacture could silently push an update to reveal the keys? but the semantics of a label aren't important. I think the important question is should an authority be able to read messages and if so, under what circumstances? What if it's to prevent a major terrorist attack, should you have an absolute right to privacy so much so that, a means that would never be used against you can't exist even if it means the loss of a lot of life? As I say, I think the question should be around where we draw the line and what protections we put in place to ensure it's not crossed.