File

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.

-- mod_muc_mam_markers
--
-- Copyright (C) 2019 Marcos de Vera Piquero <marcos.devera@quobis.com>
--
-- This file is MIT/X11 licensed.
--
-- A module to make chat markers get stored in the MUC archives
--

module:depends"muc_mam"

local function handle_muc_message (event)
	local stanza = event.stanza;
	local is_received = stanza:get_child("received", "urn:xmpp:chat-markers:0");
	local is_displayed = stanza:get_child("displayed", "urn:xmpp:chat-markers:0");
	local is_acked = stanza:get_child("acknowledged", "urn:xmpp:chat-markers:0");
	if (is_received or is_displayed or is_acked) then
		return true;
	end
	return nil;
end

module:hook("muc-message-is-historic", handle_muc_message);

module:log("debug", "Module loaded");