Mercurial > prosody-modules
view mod_omemo_all_access/README.markdown @ 4629:0e60ce83205c
mod_s2s_keepalive: Ignore errors from the local server
If a stanza can't be delivered and instead an bounce is generated, the
origin of the error, when different from the stanza 'from' should be
indicated in the 'by' attribute of the <error>, which we look for here
so this doesn't count as a successful ping.
An error that does come from the remote means we have connectivity, but
probably no XEP-0199 handling. This is fine. We care about connectivity,
not protocol.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Wed, 21 Jul 2021 15:57:13 +0200 |
| parents | b5f5d6bf703c |
| children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'Disable access control for all OMEMO related PEP nodes' --- Introduction ============ Traditionally OMEMO encrypted messages could only be exchanged after gaining mutual presence subscription due to the OMEMO key material being stored in PEP. XEP-0060 defines a method of changing the access model of a PEP node from `presence` to `open`. However Prosody does not yet support access models on PEP nodes. This module disables access control for all OMEMO PEP nodes (=all nodes in the namespace of `eu.siacs.conversations.axolotl.*`), giving everyone access to the OMEMO key material and allowing them to start OMEMO sessions with users on this server. Disco feature ============= This modules annouces a disco feature on the account to allow external tools such as the [Compliance Tester](https://conversations.im/compliance/) to check if this module has been installed. Compatibility ============= ----- ----------------------------------------------------------------------------- trunk Not needed, mod\_pep provides this feature already 0.11 Not needed, mod\_pep provides this feature already 0.10 Works ----- -----------------------------------------------------------------------------