view mod_muc_block_pm/mod_muc_block_pm.lua @ 6319:04c3273cb81f

mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents 67f7df9892bb
children
line wrap: on
line source

local st = require "util.stanza";

module:hook("muc-disco#info", function(event)
	table.insert(event.form, { name = "muc#roomconfig_allowpm"; value = "moderators" });
end);

module:hook("muc-private-message", function(event)
	local stanza, room = event.stanza, event.room;
	local from_occupant = room:get_occupant_by_nick(stanza.attr.from);

	if from_occupant and from_occupant.role == "moderator" then
		return -- moderators may message anyone
	end

	local to_occupant = room:get_occupant_by_nick(stanza.attr.to)
	if to_occupant and to_occupant.role == "moderator" then
		return -- messaging moderators is ok
	end

	if to_occupant.bare_jid == from_occupant.bare_jid then
		return -- to yourself is okay, used by some clients to sync read state in public channels
	end

	room:route_to_occupant(from_occupant, st.error_reply(stanza, "cancel", "policy-violation", "Private messages are disabled", room.jid))
	return false;
end, 1);