[OMEMO] Psi XMPP Client does not work correctly with all Openfire XMPP based Servers

[Neustradamus]

Dear @psi-im team, @psi-plus team, @Ri0n, @Vitozz, @tehnick,

There is an historical OMEMO bug with Openfire XMPP based Servers, this one for example: https://igniterealtime.org/.

Example (2 XMPP Accounts on 2 different XMPP Servers: jabber.org and igniterealtime.org):

• [email protected] has OMEMO fingerprints of [email protected] (GOOD)
• [email protected] has not OMEMO fingerprints of [email protected] (NOT GOOD)

Example 2 (2 XMPP Accounts on same XMPP Server: igniterealtime.org):

• [email protected] has not OMEMO fingerprints of [email protected] (NOT GOOD)
• [email protected] has not OMEMO fingerprints of [email protected] (NOT GOOD)

Can you look it?

---

No problem with all other XMPP Servers: ejabberd, Prosody IM and Tigase XMPP Server.

---

IMPORTANT and STRANGE: it has not been tested by me but some people said that OMEMO works without any problems with Openfire and another XMPP Clients.

---

EDIT: I have done all diagnostics about it: Openfire has a problem with PubSub/PEP and not only for OMEMO, but it is linked to all <message to="[email protected]/client" from="[email protected]" type="headline">:

<items node="http://jabber.org/protocol/activity">

<items node="http://jabber.org/protocol/mood">

<items node="http://jabber.org/protocol/tune">

<items node="http://jabber.org/protocol/geoloc">

<items node="eu.siacs.conversations.axolotl.devicelist">

<items node="urn:xmpp:avatar:metadata">

At the same time, it has been missing:

<feature var="urn:xmpp:bookmarks:1#compat"/>
<feature var="urn:xmpp:bookmarks:1#compat-pep"/>

All details in my following comments.

---

Note: This ticket has not been published several years ago.

cc: @stigger, @stokito (a recent contributor).