Converse.js v4.2.0 unable send OMEMO message

[David]

Hi Dev!
I state that I don't know if this could be a libsignal bug, I've try to ask on Github Converse.js without answer.

I've just installed (from git) on VPS Debian Stretch, Prosody 0.11, Fail2ban 0.9.6-2, Shorewall 5.0.15.6-1, Apache 2.4.25, modsecurity 3.0.0-3, php7 7.0.33, Converse.js v4.2.0, gitted libsignal-protocol-javascript and include it into converse html code.

I write just to understand if it could be a Libsingal or a Converse.js problem. If possible.

Here my Converse installation.

Thanks!

[Scott Nonnenberg]

This is not the right place for that kind of discussion. You might find someone who can help you here: https://whispersystems.discoursehosting.net/

[David]

Thanks!

[chee]

@danjde did you have any luck?

[David]

No, I've try to write as suggested by @scottnonnenberg to Signal Community, with no luck.
It's a Converse 4.2.0 bug, surely.
I think the Converse.js developer will correct the problem even if for now he doesn't answer
I've add a task on OMEMO too, where @licaon-kter says it works, although I have very serious doubts ;-)

[Licaon_Kter]

Yes it does, at least in 1:1, MUC might have issues, cleaning/regen keys might have others.

[chee]

v4.2.0 does not work for me, when trying to send an OMEMO message the box remains greyed out. However, receiving OMEMO messages from the other user works fine. The error is Error: Invalid signature from libsignal-protocol.min.js. However, it works just fine on v4.1.2

[Licaon_Kter]

@chee can you try with the normal version instead of .min.js? Where did you get the minified one?

[David]

I've try with the "normal" version, not min.js, same result: don't start on OMEMO mode.

[Licaon_Kter]

Other clients work ok with OMEMO? Conversations? Dino? Gajim?

[David]

licaon-kter: Other clients work ok with OMEMO? Conversations? Dino? Gajim?

Perfectly.