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.

#!/usr/bin/env python2

import sys

def auth(username, password):
	if username == "someone":
		return "1"
	return "0"

def respond(ret):
	sys.stdout.write(ret+"\n")
	sys.stdout.flush()

methods = {
	"auth": { "function": auth, "parameters": 2 }
}

while 1:
	line = sys.stdin.readline().rstrip("\n")
	method, sep, data = line.partition(":")
	if method in methods:
		method_info = methods[method]
		split_data = data.split(":", method_info["parameters"])
		if len(split_data) == method_info["parameters"]:
			respond(method_info["function"](*split_data))
		else:
			respond("error: incorrect number of parameters to method '%s'"%method)
	else:
		respond("error: method '%s' not implemented"%method)