mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

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