Software /
code /
prosody-modules
File
mod_block_outgoing/mod_block_outgoing.lua @ 5810:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parent | 2007:dc1299ca0185 |
line wrap: on
line source
-- Module to block all outgoing stanzas from a list of users local jid_bare = require "util.jid".bare; local is_admin = require "core.usermanager".is_admin; local set = require "util.set"; local block_users = module:get_option_set("block_outgoing_users", {}); local block_all = block_users:empty(); local stanza_types = module:get_option_set("block_outgoing_stanzas", { "message" }); local jid_types = set.new{ "host", "bare", "full" }; local function block_stanza(event) local stanza = event.stanza; local from_jid = jid_bare(stanza.attr.from); if stanza.attr.to == nil or stanza.attr.to == module.host or is_admin(from_jid, module.host) then return; end if block_all or block_users:contains(from_jid) then module:log("debug", "Blocked outgoing %s stanza from %s", stanza.name, stanza.attr.from); return true; end end function module.load() for stanza_type in stanza_types do for jid_type in jid_types do module:hook("pre-"..stanza_type.."/"..jid_type, block_stanza, 10000); end end end