Ejabberd and Conversations using OMEMO

ejabberdxmpp

I'm new to XMPP Servers and have setup a ejabberd server 18.09 under Windows 7 and I'm using Conversations 2.3.4+fcr as client.
Now I want to use OMEMO and I have no success. Conversations says in its server info, that XEP-0163 has failed and when I want to write a OMEMO encrypted message Conversations is complaining about missing device list.

I understand that OMEMO encryption is based on the existing device list in ejabberd server. Ejabberd knows the device, I can see Conversations.something as device in the online user list.

Configuration file of ejabberd is like this:

force_node_config: 
"eu.siacs.conversations.axolotl.*": 
access_model: whitelist

Conversations says in CATLOG:

AxolotlService: Have no target devices in PEP!

At the moment I'm running out of ideas, any help would be appreciated…

Best Answer

The default config for 18.12 came with this in the config

force_node_config:
  ## Change from "whitelist" to "open" to enable OMEMO support
  ## See https://github.com/processone/ejabberd/issues/2425

Related Solutions

Amazon EC2 with XMPP infrastructure

You need to point your xmpp hostnames to the EC2 instances, either using CNAME records to Amazon's hostnames:

xmpp1.example.com.  IN  CNAME   ec2-192-0-2-76.us-west-1.compute.amazonaws.com.

or using A records directly to the IP:

xmpp1.example.com.  IN  A   192.0.2.76

The advantage of the CNAME approach is that other EC2 instances looking up the name will resolve to the internal IP. Your SRV records should stay the same as before, and simply point to xmppN.example.com.

If you don't use Elastic IPs the instances will get different IPs each time they are started. If updating DNS every time this happens isn't feasible then you have to use Elastic IPs.

I've never heard of XMPP requiring PTR records to match the forward lookup, this is usually only necessary for SMTP. I've run XMPP servers where this hasn't been the case and haven't had any problems. If you really want this, Amazon do let you configure reverse lookups for Elastic IPs, but this is intended for mail servers and so you may need to convince them that you need this.

Related Topic