Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot receive OMEMO messages from Gajim or ChatSecure

See original GitHub issue

First, thank you for this great peace of software. Second, I wanted to try the OMEMO encryption, so I integrated libsignal into 4.0.0 as told in https://github.com/conversejs/converse.js/issues/497#issuecomment-419606466.

The lock appears and I can send OMEMO encrypted messages. However, if I want to reply from another client, conversejs is not showing anything. I only get

New remote ephemeral key

from libsignal in debug. I tried with ChatSecure and Gajim.

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

siikamiikacommented, Oct 13, 2018

I just confirmed that OMEMO encrypted messages work from Gajim to converse.js again if I add this to Gajim’s OMEMO plugin:

diff --git a/omemo/omemo_connection.py b/omemo/omemo_connection.py
index c1cbf52..6ce0baa 100644
--- a/omemo/omemo_connection.py
+++ b/omemo/omemo_connection.py
@@ -546,6 +546,9 @@ class OMEMOConnection:
                     error=error, time_=time.time(), session=event.session))
             return
 
+        body = Node('body', payload='asdf')
+        event.msg_iq.addChild(node=body)
+
         encrypted_node = OmemoMessage(msg_dict)
         event.msg_iq.addChild(node=encrypted_node)

Not sure who’s not following the spec, but at least this could be fixed in either client and Gajim isn’t the only client with this problem.

0reactions

jcbrandcommented, Oct 13, 2018

@siikamiika Excellent work, thanks for drilling down to find the problem.

According to XEP-0384, the <payload> corresponds to the message’s <body>, so I think it should be fine for a message to not have a <body> tag.

I’ll fix asap.