ejabberd

How does this affect servers like ejabberd? I just noticed that they upgraded their server yesterday [0] and am wondering if it could contain some kind of fix for this, or would this be unrelated? [0] https://github.com/processone/ejabberd/releases

@wut42: No, it was ejabberd! - https://docs.ejabberd.im/use-cases/ Mongoose IM is a fork of ejabberd: - https://www.ejabberd.im/ - https://github.com/processone/ejabberd

Actually, they still do (or do again?). Here comes the relevant part from their example config [1]: force_node_config: ## Change from "whitelist" to "open" to enable OMEMO support ## See https://github.com/processone/ejabberd/issues/2425 "eu.siacs.conversations.axolotl.*": access_model: whitelist [1] https://github.com/processone/ejabberd/blob/master/ejabberd....

ejabberd [0], XMPP server is written in erlang and powers chat in some of the biggest MMORPGs [1]. [0]: https://github.com/processone/ejabberd [1]: https://xmpp.org/uses/gaming.html

Sadly I don't. I have mine running since a while, and some things might not be state-of-the-art anymore. The server doesn't really have to support end-to-end encryption as that is part of the clients (in fact, there are some server-side extensions which have to be present, but those are mostly enabled by default). Afaik, the default ejabberd configuration is very close to what you need, and there is just one part that you have to remove to enable OMEMO [1]. I don't understand why but recently the ejabberd devs introduced that part to their default configuration which makes it harder to use end-to-end encryption. Nevertheless, if you are very interested in a detailed guide, I could write one as I am thinking about setting up a secondary server as a testing environment. [1]: https://github.com/processone/ejabberd/blob/master/ejabberd....

Or XMPP+OMEMO which adds things like multi-client support and encrypted group chat: https://news.ycombinator.com/item?id=13396083 I'm running this on my own server (using ejabberd [1] as Prosody - which I used previously - still has problems with some of the required XEPs[2]) using several different clients (Conversations [3] on Android, Pidgin on Linux, etc). The one weak link in OMEMO is the difficulty of verifying the authenticity of the device key signatures used by communication counterparts. These signatures are 64-character hexadecimal strings which the user is supposed to verify being authentic before initiating encrypted communications. Humans as not very good at this task, computer can help but they can also be tampered with. There are ways around this problem - e.g. meeting up in person before initiating communications (viz. PG

btw. very much agree most of the clients are inadequate but if I could humbly pimp Openfire (I'm a dev there): https://github.com/igniterealtime/Openfire And ejabberd of course (powering WhatsApp): https://github.com/processone/ejabberd You'll see that on the server side at least XMPP is very well catered for.

Like brogondwana says, from the commit log on their github repo, it's clear (years after that fastmail blog post) that Process One has abandoned ejabberd 3.x. ejabberd 2.x appears to continue to have updates. [0] Having said that, for my single-account, single-site needs, ejabberd worked just fine for me for the several years between the time that I learned about the fact that Google Talk federated with XMPP servers and the time that Google stopped federating with other XMPP server operators. I can't speak to how comprehensive ejabberd is, but for one-on-one chats, and multi-user chats, it worked just fine when I was using it. [0] https://github.com/processone/ejabberd