Software / code / prosody-modules
Annotate
mod_require_otr/README.markdown @ 5810:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Thu, 07 Dec 2023 15:46:50 +0000 |
| 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 ------ ------- |
