view mod_require_otr/README.markdown @ 4326:f6fdefc5c6ac

mod_roster_command: Fix subscription when the "user JID" is a bare domain. Do not attempt to update the roster when the user is bare domain (e.g. a component), since they don't have rosters and the attempt results in an error: $ prosodyctl mod_roster_command subscribe proxy.example.com contact@example.com xxxxxxxxxxFailed to execute command: Error: /usr/lib/prosody/core/rostermanager.lua:104: attempt to concatenate local 'username' (a nil value) stack traceback: /usr/lib/prosody/core/rostermanager.lua:104: in function 'load_roster' /usr/lib/prosody/core/rostermanager.lua:305: in function 'set_contact_pending_out' mod_roster_command.lua:44: in function 'subscribe'
author Boris Grozev <boris@jitsi.org>
date Tue, 05 Jan 2021 13:15:00 -0600
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
  ------ -------