search

psi-im / plugins

Officially supported Psi plugins
56 stars 24 forks source link

OMEMO is forcing: *** [OMEMO] Unable to build any sessions, the message was not sent #54

Closed Neustradamus closed 2 years ago

Neustradamus commented 4 years ago

A contact has not OMEMO (it is specified by the client), the OMEMO icon is in grey and the mouse on it says:

When we send a message to a contact, it is forced by OMEMO (not unencrypted message):

There is no possibility to send unencrypted messages in the chat window of the contact, the icon is in grey and disabled.

Right click on our account in roster -> XML Console -> JID -> the contact@domain.tld -> enable checked

Result for a sent message: Nothing, it is empty.

There is no OMEMO fingerprint for this contact in the client -> Options -> Plugins -> OMEMO plugin -> Fingerprints

Linked to:

ortuman commented 4 years ago

To give more context, from server PoV no XMPP payload is received at all. So whatever is going on, seems it only occurs on client side.

Neustradamus commented 4 years ago

@stigger: Any news about this historical OMEMO bug?

I am very good, I have done a screenshot only for you:

Problem: Grey icon, OMEMO is automatically forced, impossible to disable OMEMO for this contact.

Neustradamus commented 4 years ago

@tehnick: I confirm that the bug is always here with your last build:

Neustradamus commented 3 years ago

@kssytsrk: Can you look this ticket?

kssytsrk commented 3 years ago

Might this be a result of Options > Plugins > OMEMO plugin settings > Configuration > OMEMO encryption policy being set to "Always enabled"? I have it set to "Disabled by default", and can't reproduce on Psi+ 1.5.1551 (2021-08-16) / FreeBSD 13.0.

Neustradamus commented 3 years ago

I have "Disabled by default".

Neustradamus commented 3 years ago

@kssytsrk: Thanks for your reply.

Can you test with 2 new test accounts without OMEMO used before?

Please use Psi+ and Psi+.

You will find the problem...

Neustradamus commented 2 years ago

@tehnick: Example of the problem today with a roster contact who does not have/use OMEMO:

In tab, the OMEMO icon is in grey "OMEMO encryption is not available for this contact".

When I send a simple message, it is OMEMO forced, no possibility to change it... [XX:XX:XX] *** [OMEMO] Unable to build any sessions, the message was not sent [XX:XX:XX] Test

<iq id='XXXXXX' from='me@domain.tld' to='contact@domain.tld' type='get'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items node='eu.siacs.conversations.axolotl.devicelist'/>
</pubsub>
</iq>

<iq type="result" from="contact@domain.tld" to="me@domain.tld/client" id="XXXXXX">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<items node="eu.siacs.conversations.axolotl.devicelist">
<item id="current">
<list xmlns="eu.siacs.conversations.axolotl">
<device id="XXXXXXXXX"/>
<device id="XXXXXXXXXX"/>
</list>
</item>
</items>
</pubsub>
</iq>

I have the same problem with the same contact in a MUC Room with "Role that May Discover Real JIDs of Occupants : Anyone" and 1:1 PM messages disabled (normal member, not admin). No problem if "Role that May Discover Real JIDs of Occupants : Moderator" and 1:1 PM messages disabled (normal member, not admin)

Neustradamus commented 2 years ago

@nullobsi: I have this problem with you in the client...