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.

author "Kim Alvefur <zash@zash.se>"
description "Prosody XMPP server"

# Normal runlevel based start and stop
start on runlevel [2345]
stop on runlevel [!2345]

# Alternate method for starting and stopping
# when a network interface comes and goes
#
# start on net-device-up IFACE=eth0
# stop on net-device-down IFACE=eth0

# Change user so Prosdy doesn't have to
setgid prosody
setuid prosody

# Set a sensible umask
umask 0027

# Run prosody
exec /usr/bin/prosody

# Collect stdout into a log file
console log

# Restart on crashes
respawn
respawn limit 5 10