You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.
I've only recently started to use XMPP/OMEMO with profanity which works great
(even though the install process was rather cumbersome).
I noticed the open TODO task "Handle messages from own devices".
I'm using multiple devices to send messages:
A Laptop with profanity client and this plugin
B Mobile with conversations app
I noticed that with XEP-280 Carbon Copy enabled, when I send a message from A (B) to recipient X, it also gets delivered to device B (A). However, the message content cannot be displayed, I supposed because it is encrypted for X only.
When a client sends a eligible for carbons delivery, its sending server delivers the according to RFC 6120 and RFC 6121, and delivers a forwarded copy to each Carbons-enabled resource for the matching bare JID sender, excluding the sending client. Note that this happens irrespective of whether the sending client has carbons enabled.
Where in this process is OMEMO supposed to encrypt forwarded copy to carbon-enabled resources?
Am I correct in the assumption that encryption is executed by XMPP client (here with Python based OMEMO plugin) prior to handing the message over to the server? So how can this work?
The resulting protocol was designed to allow for the following primary usage scenarios:
Automatic history synchronization between multiple clients.
...
Thank you very much for the great work and sharing your insights and ideas!
The text was updated successfully, but these errors were encountered:
Hi,
I've only recently started to use XMPP/OMEMO with profanity which works great
(even though the install process was rather cumbersome).
I noticed the open TODO task "Handle messages from own devices".
I'm using multiple devices to send messages:
A Laptop with profanity client and this plugin
B Mobile with conversations app
I noticed that with XEP-280 Carbon Copy enabled, when I send a message from A (B) to recipient X, it also gets delivered to device B (A). However, the message content cannot be displayed, I supposed because it is encrypted for X only.
As XEP-0280 Message Carbons Sending describes:
Where in this process is OMEMO supposed to encrypt forwarded copy to carbon-enabled resources?
Am I correct in the assumption that encryption is executed by XMPP client (here with Python based OMEMO plugin) prior to handing the message over to the server? So how can this work?
Or would the synchronisation rather be handled by XEP-0313: Message Archive Management which reads:
Thank you very much for the great work and sharing your insights and ideas!
The text was updated successfully, but these errors were encountered: