While XMPP clients work consistently well, OMEMO seems to not always work how it has worked before according to memory or to notes. While communication to the server is encrypted, communication needs OMEMO to be secure through the server as well, so only endpoints can view the data.
In the past, dependencies mostly related to cryptography had to be updated, to get OMEMO in working status again.
OMEMO versions
The newest implementation of OMEMO uses the namespace of "urn:xmpp: omemo:2" since XEP-0384 version 0.8.0 released in late 2021. OMEMO:1 which used "urn:xmpp: omemo:1" was intended as the future proof version. I'm uncertain if OMEMO:2 is compatible with OMEMO:1. OMEMO:0 is obsolete, which Siacs OMEMO previously replaced.
The most widespread implementation of OMEMO has been Siacs OMEMO stewarded by Conversations, which has used the namespace of "eu.siacs.conversations.axolotl". This was for XEP-0384 versions 0.2.0 until 0.3.0. This Siacs version of OMEMO is incompatible with other versions of OMEMO. As of January 2021, Conversations has been using Siacs OMEMO. Since then, uncertain which version of OMEMO Conversations currently uses. https://wiki.xmpp.org/web/Tech_pages/OMEMO
Histories of namespaces used by OMEMO (and subsequently its versions) are included in https://xmpp.org/extensions/xep-0384.html. Also to note, while OMEMO (XEP-0384) is an experimental standard, its implementations for certain sets of messengers are standards as features.
OMEMO client/server status
https://compliance.conversations.im/ indicates if an XMPP server has compatibility with the OMEMO version that Conversations uses, and it also indicates compatibility of servers with other XMPP extensions (XEP's) which Conversations also uses.
https://omemo.top/ has the status on any implementation of OMEMO for XMPP clients. The site has been around for a few years, yet development of OMEMO on XMPP seems to have halted on some clients. The bounty website is down at the time of this writing. Some other links are outdated as well.
Mozilla has an XMPP feature for Thunderbird, but there's no OMEMO extension for it.
In the past, net-im/gajim, and net-im/dino have worked well with OMEMO on FreeBSD. Gajim version 1.8.1 uses Siacs OMEMO, while the current Gajim version available on FreeBSD is 1.3.3. OMEMO for XMPP on net-im/pidgin (through net-im/lurch) has worked recently with mixed results. Uncertain of the reasons that these haven't worked well recently, whether it has to do with different OMEMO versions being on each client, or my computer configuration.
There's net-im/coyim (in Golang) which usesOMEMO encryption (OTR) by default, and doesn't need it to be configured. On FreeBSD, at least, it requires use of Tor. While that's great for some people's purposes, that can be excessive for the average need.
Libervia and Moxxy, not available on FreeBSD, have been used with OMEMO:2. https://xmpp.org/2023/08/the-xmpp-newsletter-june-july-2023/ https://libervia.org/news. Twomemo is an OMEMO:2 backend for Python.
Leave updates or share your experience on what you use with XMPP OMEMO on FreeBSD, including for use between FreeBSD and mobile devices. Tell which client you use on FreeBSD for OMEMO on XMPP/Jabber, or what has worked for you.
In the past, dependencies mostly related to cryptography had to be updated, to get OMEMO in working status again.
OMEMO versions
The newest implementation of OMEMO uses the namespace of "urn:xmpp: omemo:2" since XEP-0384 version 0.8.0 released in late 2021. OMEMO:1 which used "urn:xmpp: omemo:1" was intended as the future proof version. I'm uncertain if OMEMO:2 is compatible with OMEMO:1. OMEMO:0 is obsolete, which Siacs OMEMO previously replaced.
The most widespread implementation of OMEMO has been Siacs OMEMO stewarded by Conversations, which has used the namespace of "eu.siacs.conversations.axolotl". This was for XEP-0384 versions 0.2.0 until 0.3.0. This Siacs version of OMEMO is incompatible with other versions of OMEMO. As of January 2021, Conversations has been using Siacs OMEMO. Since then, uncertain which version of OMEMO Conversations currently uses. https://wiki.xmpp.org/web/Tech_pages/OMEMO
Histories of namespaces used by OMEMO (and subsequently its versions) are included in https://xmpp.org/extensions/xep-0384.html. Also to note, while OMEMO (XEP-0384) is an experimental standard, its implementations for certain sets of messengers are standards as features.
OMEMO client/server status
https://compliance.conversations.im/ indicates if an XMPP server has compatibility with the OMEMO version that Conversations uses, and it also indicates compatibility of servers with other XMPP extensions (XEP's) which Conversations also uses.
https://omemo.top/ has the status on any implementation of OMEMO for XMPP clients. The site has been around for a few years, yet development of OMEMO on XMPP seems to have halted on some clients. The bounty website is down at the time of this writing. Some other links are outdated as well.
Mozilla has an XMPP feature for Thunderbird, but there's no OMEMO extension for it.
In the past, net-im/gajim, and net-im/dino have worked well with OMEMO on FreeBSD. Gajim version 1.8.1 uses Siacs OMEMO, while the current Gajim version available on FreeBSD is 1.3.3. OMEMO for XMPP on net-im/pidgin (through net-im/lurch) has worked recently with mixed results. Uncertain of the reasons that these haven't worked well recently, whether it has to do with different OMEMO versions being on each client, or my computer configuration.
There's net-im/coyim (in Golang) which uses
Libervia and Moxxy, not available on FreeBSD, have been used with OMEMO:2. https://xmpp.org/2023/08/the-xmpp-newsletter-june-july-2023/ https://libervia.org/news. Twomemo is an OMEMO:2 backend for Python.
Leave updates or share your experience on what you use with XMPP OMEMO on FreeBSD, including for use between FreeBSD and mobile devices. Tell which client you use on FreeBSD for OMEMO on XMPP/Jabber, or what has worked for you.