File

mod_s2s_blacklist/mod_s2s_blacklist.lua @ 5173:460f78654864

mod_muc_rtbl: also filter messages This was a bit tricky because we don't want to run the JIDs through SHA256 on each message. Took a while to come up with this simple plan of just caching the SHA256 of the JIDs on the occupants. This will leave some dirt in the occupants after unloading the module, but that should be ok; once they cycle the room, the hashes will be gone. This is direly needed, otherwise, there is a tight race between the moderation activities and the actors joining the room.
author Jonas Schäfer <jonas@wielicki.name>
date Tue, 21 Feb 2023 21:37:27 +0100
parent 2893:d958558e0058
line wrap: on
line source

local st = require "util.stanza";

local blacklist = module:get_option_inherited_set("s2s_blacklist", {});

module:hook("route/remote", function (event)
	if blacklist:contains(event.to_host) then
		if event.stanza.attr.type ~= "error" then
			module:send(st.error_reply(event.stanza, "cancel", "not-allowed", "Communication with this domain is restricted"));
		end
		return true;
	end
end, 100);

module:hook("s2s-stream-features", function (event)
	if blacklist:contains(event.origin.from_host) then
		event.origin:close({
			condition = "policy-violation";
			text = "Communication with this domain is restricted";
		});
	end
end, 1000);