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-Alpha'
summary: 'Store who created the invite to create a user account'
...

Introduction
============

Invites are an intermediate way between opening registrations completely and
closing registrations completely.

By letting users invite other users to the server, an administrator exposes
themselves again to the risk of abuse.

To combat that abuse more effectively, this module allows to store (outside
of the user’s information) who created an invite which was used to create the
user’s account.

Details
=======

Add to `modules_enabled`.

Caveats
=======

- The information is not deleted even when the associated user accounts are
  deleted.
- Currently, there is no way to make any use of that information.