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 block_groupchat = module:get_option_boolean("otr_block_groupchat", false);

function reject_plaintext_messages(event)
    local body = event.stanza:get_child_text("body");
    if body and body:sub(1,4) ~= "?OTR" or (not block_groupchat and event.stanza.attr.type == "groupchat") then
        return event.origin.send(st.error_reply(event.stanza, "modify", "policy-violation", "OTR encryption is required for conversations on this server"));
    end
end

module:hook("pre-message/bare", reject_plaintext_messages, 300);
module:hook("pre-message/full", reject_plaintext_messages, 300);
module:hook("pre-message/host", reject_plaintext_messages, 300);