Mercurial > prosody-modules
annotate mod_require_otr/README.markdown @ 4515:2e33eeafe962
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked
Original intention was to leave alone things that this module isn't
handling. However markers in archives are just problematic without
more advanced logic about what is markable and what is not. It also
requires a more advanced query in mod_muc_rai to determine the latest
markable message instead of the latest archived message.
I'd rather keep the "is archivable" and "is markable" definition the
same for simplicity. I don't want to introduce yet another set of rules
for no reason.
No markers in MAM.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Mon, 22 Mar 2021 15:55:02 +0000 |
| parents | 4d73a1a6ba68 |
| children |
| rev | line source |
|---|---|
| 1803 | 1 --- |
| 2 labels: | |
| 3 - 'Stage-Stable' | |
| 4 summary: 'Enforce a policy for OTR-encrypted messages' | |
| 5 ... | |
| 6 | |
| 7 Introduction | |
| 8 ------------ | |
| 9 | |
| 10 [OTR, "Off The Record"](https://otr.cypherpunks.ca/), encryption allows | |
| 11 clients to encrypt messages such that the server cannot read/modify | |
| 12 them. | |
| 13 | |
| 14 This module allows the server admin to require that all messages are | |
| 15 OTR-encrypted. | |
| 16 | |
| 17 Configuration | |
| 18 ------------- | |
| 19 | |
| 20 Just enable the module by adding it to your global `modules_enabled`, or | |
| 21 if you only want to load it on a single host you can load it only for | |
| 22 one host like this: | |
| 23 | |
| 24 VirtualHost "example.com" | |
| 25 modules_enabled = { "require_otr" } | |
| 26 | |
| 27 #### Compatibility | |
| 28 | |
| 29 ------ ------- | |
| 30 0.10 Works | |
| 31 0.9 Works | |
| 32 0.8 Works | |
| 33 ------ ------- |