OMEMO Key Handling not stable in groups/conferences about plugins HOT 10 OPEN

omemoplugin is based on libsignal-protocol-c, is there any alternative possible? signalapp and its libraries are not packaged in Fedora. I know this discussion has happened several times. Can the developers elaborate or sum up the reasons another time, please?
https://github.com/signalapp/libsignal-protocol-c

from plugins.

omemoplugin is based on libsignal-protocol-c, is there any alternative possible?

No.

signalapp and its libraries are not packaged in Fedora.

What is the problem to prepare package with libsignal-protocol-c for Fedora? In Debian and Ubuntu we have one since 2017. Unfortunately, it is outdated. I would suggest you to use latest version of library in Fedora.

Can the developers elaborate or sum up the reasons another time, please?

IIRC there are no free and open-source alternatives for this library at all.

from plugins.

@ulfi OMEMO for MUC has two requirements:

• JIDs of the participants are available to everyone;
• all participants support OMEMO.

Please make sure that both of these requirements are met in your case. For troubleshooting you can also try to have an OMEMO-encrypted conversations with individual MUC participants to figure out, which one is causing the problem.

Psi+ don't enter well after restart mainly this (encrypted) conferences

Please provide a more detailed description of the problem.

from plugins.

In a protected mucroom, 3 accounts:

• [XX:XX:XX] *** [OMEMO] Unable to build any sessions, the message was not sent
  or
• Nothing when we sent OMEMO messages (nothing in the window, and nothing for other people)

2 accounts:

• [XX:XX:XX] *** [OMEMO] Unable to build any sessions, the message was not sent
  or
• When we send a simple message without OMEMO by the second account, it is seen by sender but not by the other guy.

from plugins.

I have tested OMEMO in protected mucroom with @Ri0n, maybe he can confirm the problem and explain better than me?

from plugins.

The problem may be related with another problem: sometimes our OMEMO plugin cannot correctly detect that xmpp-client of collocutor has OMEMO support.

from plugins.

Error exists since a very long time for 1:1 chat:

• *** [OMEMO] Unable to build any sessions, the message was not sent

OMEMO is forced, it is not possible to disable OMEMO.

Linked to:

• #54

from plugins.

Try Psi+ 1.4.1299 or newer please.

from plugins.

@kssytsrk: Can you look this ticket?

from plugins.

@ulfi, @rapgro: Do you confirm that the problem is always here with current Psi+ build?
It is very important to reply...

from plugins.