3 ms·
The story is not quite the same for XMPP. For example, with XMPP you can determine ahead of time whether or not a contact has OMEMO. And clients configured to o
by MattJ100 5y ago
The story is not quite the same for XMPP. For example, with XMPP you can determine ahead of time whether or not a contact has OMEMO. And clients configured to only use OMEMO won't "fall back".
- approxim8ion 5y agoApologies, clearly my understanding of XMPP is not the best. However, both points you mentioned are client dependent, right?
- giantrobot 5y agoThe fallback has to be client dependent. With E2EE the server can't decrypt messages. So there's no way for the server to decrypt the message to "downgrade" the channel. The client is also the node responsible for encrypting all messages for all recipients so it has to know if any of those recipients haven't done a key exchange.
- MattJ100 5y agoYes. It's client-dependent for all other systems too. For example Signal's end-to-end encryption only works if both parties are using Signal. For XMPP the difference is that there are multiple E2EE clients to choose from (see https://omemo.top/ https://omemo.top/ ). And if someone chooses to use a none E2EE client, you still have the choice whether to communicate with them without E2EE, if that's acceptable to you in the specific context (not all conversations demand E2EE).