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.

Developer Utilities/Tests
=========================

This directory exists for reasons of sanity checking.  If you wish
to run the tests, set up Prosody as you normally would, and install the LDAP
modules as normal as well.  Set up OpenLDAP using the configuration directory
found in this directory (slapd.conf), and run the following command to import
the test definitions into the LDAP server:

    ldapadd -x -w prosody -D 'cn=Manager,dc=example,dc=com' -f posix-users.ldif

Then just run prove (you will need perl and AnyEvent::XMPP installed):

    prove t