Mercurial > prosody-modules

view mod_require_otr/README.markdown @ 5264:d3ebaef1ea7a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_http_oauth2: Correctly verify OAuth client credentials on revocation Makes no sense to validate against username and password here, or using a token to revoke another token, or itself? In fact, upon further discussion, why do you need credentials to revoke a token? If you are not supposed to have the token, revoking it seems the most responsible thing to do with it, so it should be allowed, while if you are supposed to have it, you should be allowed to revoke it.
author Kim Alvefur <zash@zash.se>
date Tue, 21 Mar 2023 21:57:18 +0100
parents 4d73a1a6ba68
children
line wrap: on
line source

---
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
  ------ -------