Software /
code /
prosody-modules
Annotate
mod_require_otr/README.markdown @ 5931:d194d1012fd3
Updating dox for mod_rest. Ideas expressed / clarified:
1) Making clear that mod_rest isn't to be installed under VirtualHosts AND as a component.
2) Understanding some of the implications of this choice:
A) Changes to user authentication
B) How it affects subdomains
3) More consistent use of domain names for clarity.
4) Using different heading sizes to show scope of section.
Essentially, I added all the tidbits I had to clarify in getting this to work in my
own example.
author | Ben Smith <bens@effortlessis.com> |
---|---|
date | Mon, 13 May 2024 13:25:13 -0700 |
parent | 1803:4d73a1a6ba68 |
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 ------ ------- |