3 ms·
Actually, they still do (or do again?). Here comes the relevant part from their example config [1]: force_node_config: ## Change from "whitelist" to
by arendtio 8y ago
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.yml.example#L223 https://github.com/processone/ejabberd/blob/master/ejabberd....
- seba_dos1 8y agoOh, my bad - it was the default config in Debian package that got changed. I assumed it originated from upstream, but I was wrong and it's actually patched by Debian maintainer: http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_18.12.1-2.debian.tar.xz http://deb.debian.org/debian/pool/main/e/ejabberd/ejabberd_1... (debian/patches/ejabberd.yml.example.diff)