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.

local st = require "util.stanza";

local destinations = module:get_option_set("spam_report_destinations", {});

function forward_report(event)
	local report = st.clone(event.report);
	report:text_tag("jid", event.jid, { xmlns = "urn:xmpp:jid:0" });

	local message = st.message({ from = module.host })
		:add_child(report);

	for destination in destinations do
		local m = st.clone(message);
		m.attr.to = destination;
		module:send(m);
	end
end

module:hook("spam_reporting/abuse-report", forward_report, -1);
module:hook("spam_reporting/spam-report", forward_report, -1);
module:hook("spam_reporting/unknown-report", forward_report, -1);