Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Meta
Q&A
Posts Tags Edits
Ask Question

Welcome to the Power Users community on Codidact!

Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.

Post History

71%
+3 −0
Q&A Linux / Android XMPP communication with OMEMO

The OMEMO encryption ecosystem for XMPP (Jabber) is split into distinct, incompatible versions. Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to ...

1 answer  ·  posted 19d ago by Michael‭  ·  last activity 6d ago by Michael‭

Question xmpp omemo
#4: Post edited by user avatar Michael‭ · 2025-04-27T15:56:02Z (10 days ago)
Dino is GTK
  • The [OMEMO][] encryption ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech].
  • > Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.
  • If I understand correctly, **OMEMO:0** is just broken; **siacs**[^siacs] encrypts content 1-on-1, but leaks metadata; **OMEMO:1** fixes the metadata and allows private group chats; and **OMEMO:2** changes the way content can be grouped.
  • I've been using **Conversations.im** on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.
  • The Qt options I know of are&hellip;
  • - KDE's own **Kaidan,** which is OMEMO:1 or higher and will not talk to Conversations.
  • - **Psi** and **Psi+,** which might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.
  • - **Dino.im** would be another possibility, but it won't accept certificate pinning for self-signed servers like mine.
  • I'm hoping not to break down and use Pidgin.[^pidgin]
  • Alternatively, I could make do with a good Android client that uses a newer version of OMEMO. There is understandable resistance for Conversations' maintainer to update to an OMEMO version that will render it incapable of communicating securely with any non-Conversations XMPP client for which it had previously done so.
  • [^siacs]: That is to say, version 0.2.x to 0.3.x
  • [^pidgin]: Nothing against Pidgin. I'm just trying to use Qt in lieu of GTK to the degree it is reasonable.
  • [omemo]: https://conversations.im/omemo/
  • [xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
  • The [OMEMO][] encryption ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech].
  • > Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.
  • If I understand correctly, **OMEMO:0** is just broken; **siacs**[^siacs] encrypts content 1-on-1, but leaks metadata; **OMEMO:1** fixes the metadata and allows private group chats; and **OMEMO:2** changes the way content can be grouped.
  • I've been using **Conversations.im** on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.
  • The Qt options I know of are&hellip;
  • - KDE's own **Kaidan,** which is OMEMO:1 or higher and will not talk to Conversations.
  • - **Psi** and **Psi+,** which might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.
  • - ~~**Dino.im** would be another possibility, but it won't accept certificate pinning for self-signed servers like mine.~~ *__Edit:__ Dino is GTK.*
  • I'm hoping not to break down and use Pidgin.[^pidgin]
  • Alternatively, I could make do with a good Android client that uses a newer version of OMEMO. There is understandable resistance for Conversations' maintainer to update to an OMEMO version that will render it incapable of communicating securely with any non-Conversations XMPP client for which it had previously done so.
  • [^siacs]: That is to say, version 0.2.x to 0.3.x
  • [^pidgin]: Nothing against Pidgin. I'm just trying to use Qt in lieu of GTK to the degree it is reasonable.
  • [omemo]: https://conversations.im/omemo/
  • [xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
#3: Post edited by user avatar Michael‭ · 2025-04-18T16:26:14Z (19 days ago)
Add Dino. Move the long footnote into the body.
  • The OMEMO encryption ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech]:
  • > Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.
  • If I understand correctly, OMEMO:0 is just broken; siacs[^siacs] encrypts content 1-on-1, but leaks metadata; OMEMO:1 fixes the metadata and allows private group chats; and OMEMO:2 changes the way content can be grouped.
  • I've been using Conversations.im on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.[^linux-client]
  • Alternatively, I could make do with a good Android client that uses a newer version of OMEMO.
  • [^siacs]: That is, version 0.2.x to 0.3.x
  • [^linux-client]: KDE's own **Kaidan** is OMEMO:1 or higher and will not talk to Conversations. **Psi** and **Psi+** might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.
  • [xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
  • The [OMEMO][] encryption ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech].
  • > Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.
  • If I understand correctly, **OMEMO:0** is just broken; **siacs**[^siacs] encrypts content 1-on-1, but leaks metadata; **OMEMO:1** fixes the metadata and allows private group chats; and **OMEMO:2** changes the way content can be grouped.
  • I've been using **Conversations.im** on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.
  • The Qt options I know of are&hellip;
  • - KDE's own **Kaidan,** which is OMEMO:1 or higher and will not talk to Conversations.
  • - **Psi** and **Psi+,** which might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.
  • - **Dino.im** would be another possibility, but it won't accept certificate pinning for self-signed servers like mine.
  • I'm hoping not to break down and use Pidgin.[^pidgin]
  • Alternatively, I could make do with a good Android client that uses a newer version of OMEMO. There is understandable resistance for Conversations' maintainer to update to an OMEMO version that will render it incapable of communicating securely with any non-Conversations XMPP client for which it had previously done so.
  • [^siacs]: That is to say, version 0.2.x to 0.3.x
  • [^pidgin]: Nothing against Pidgin. I'm just trying to use Qt in lieu of GTK to the degree it is reasonable.
  • [omemo]: https://conversations.im/omemo/
  • [xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
#2: Post edited by user avatar Michael‭ · 2025-04-18T15:18:30Z (19 days ago)
hint at what OMEMO is
  • The OMEMO ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech]:
  • > Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.
  • If I understand correctly, OMEMO:0 is just broken; siacs[^siacs] encrypts content 1-on-1, but leaks metadata; OMEMO:1 fixes the metadata and allows private group chats; and OMEMO:2 changes the way content can be grouped.
  • I've been using Conversations.im on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.[^linux-client]
  • Alternatively, I could make do with a good Android client that uses a newer version of OMEMO.
  • [^siacs]: That is, version 0.2.x to 0.3.x
  • [^linux-client]: KDE's own **Kaidan** is OMEMO:1 or higher and will not talk to Conversations. **Psi** and **Psi+** might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.
  • [xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
  • The OMEMO encryption ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech]:
  • > Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.
  • If I understand correctly, OMEMO:0 is just broken; siacs[^siacs] encrypts content 1-on-1, but leaks metadata; OMEMO:1 fixes the metadata and allows private group chats; and OMEMO:2 changes the way content can be grouped.
  • I've been using Conversations.im on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.[^linux-client]
  • Alternatively, I could make do with a good Android client that uses a newer version of OMEMO.
  • [^siacs]: That is, version 0.2.x to 0.3.x
  • [^linux-client]: KDE's own **Kaidan** is OMEMO:1 or higher and will not talk to Conversations. **Psi** and **Psi+** might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.
  • [xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
#1: Initial revision by user avatar Michael‭ · 2025-04-18T15:17:59Z (19 days ago) 
Linux / Android XMPP communication with OMEMO
The OMEMO ecosystem for XMPP (Jabber) is [split into distinct, incompatible versions][xmpp-tech]:

> Unfortunately there are different versions of OMEMO encryption existing, that are incompatible to each other.

If I understand correctly, OMEMO:0 is just broken; siacs[^siacs] encrypts content 1-on-1, but leaks metadata; OMEMO:1 fixes the metadata and allows private group chats; and OMEMO:2 changes the way content can be grouped.

I've been using Conversations.im on Android, which uses the "siacs" versions. I'm looking for a reputable Qt-based Linux XMPP client compatible with siacs OMEMO.[^linux-client]

Alternatively, I could make do with a good Android client that uses a newer version of OMEMO.


[^siacs]: That is, version 0.2.x to 0.3.x
[^linux-client]: KDE's own **Kaidan** is OMEMO:1 or higher and will not talk to Conversations. **Psi** and **Psi+** might have a compatible OMEMO version, but it's immaterial as they crash immediately upon launch.



[xmpp-tech]: https://wiki.xmpp.org/web/Tech_pages/OMEMO
xmpp omemo