Mercurial > prosody-modules
view mod_omemo_all_access/README.markdown @ 3258:85e3117b2b60
mod_pubsub_github/README: Note that it might work with Gitlab as well
Guess based on looking at this documentation:
https://developer.github.com/v3/activity/events/types/#pushevent
https://docs.gitlab.com/ee/system_hooks/system_hooks.html#push-events
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 24 Aug 2018 16:28:48 +0200 |
parents | 08f6b9d37a49 |
children | 617c65ef1a70 |
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 ============= ----- ----------------------------------------------------------------------------- 0.10 Works ----- -----------------------------------------------------------------------------