mod_require_otr/README.markdown
author Matthew Wild <mwild1@gmail.com>
Tue, 18 Jan 2022 17:01:18 +0000
changeset 4880 0f5f2d4475b9
parent 1807 4d73a1a6ba68
permissions -rw-r--r--
mod_http_xep227: Add support for import via APIs rather than direct store manipulation In particular this transitions PEP nodes and data to be imported via mod_pep's APIs, fixing issues with importing at runtime while PEP data may already be live in RAM. Next obvious candidate for this approach is rosters, so clients get immediate roster pushes and other special handling (such as emitting subscribes to reach the desired subscription state).

---
labels:
- 'Stage-Stable'
summary: 'Enforce a policy for OTR-encrypted messages'
...

Introduction
------------

[OTR, "Off The Record"](https://otr.cypherpunks.ca/), encryption allows
clients to encrypt messages such that the server cannot read/modify
them.

This module allows the server admin to require that all messages are
OTR-encrypted.

Configuration
-------------

Just enable the module by adding it to your global `modules_enabled`, or
if you only want to load it on a single host you can load it only for
one host like this:

    VirtualHost "example.com"
        modules_enabled = { "require_otr" }

#### Compatibility

  ------ -------
  0.10   Works
  0.9    Works
  0.8    Works
  ------ -------