3 ms·
OTR also breaks Message Archive Management (MAM) and Carbons - the two features making multi-client operation any useful, and highlighted in the article. And wi
by ge0rg 12y ago
OTR also breaks Message Archive Management (MAM) and Carbons - the two features making multi-client operation any useful, and highlighted in the article. And with MAM, there actually are plain-text logs of your conversations on the server.
The call is still open on end-to-end encryption over XMPP when multiple devices (or more than two parties) are involved.
- pgeorgi 12y agoThe issues you list (message archive being plain text, key management when multiple recipients are involved, maybe even transparently) don't seem to be XMPP specific. Is there any chat system out there with end-to-end crypto and reasonable support for multiple devices?
- creshal 12y agoThey aren't XMPP specific, but OTR as implemented in e.g. Pidgin goes above and beyond in making them bad – archiving is either plain text or disabled, keys cannot be changed at all (so not even manually syncing them is possible), and session handover doesn't work (there's a session management implemented, but it doesn't do anything except silently eating messages).
- ge0rg 12y agoAs funny as it sounds: iMessage. The only crypto-related problem with iMessage's encryption is that Apple controls the key servers. -- http://techcrunch.com/2014/02/27/apple-explains-exactly-how-secure-imessage-really-is/ http://techcrunch.com/2014/02/27/apple-explains-exactly-how-... Besides, it is not available for non-Apple devices. TextSecure/Signal has a robust crypto system, and they are working on multi-device support.