Software /
code /
prosody-modules
File
mod_host_blacklist/mod_host_blacklist.lua @ 5185:09d6bbd6c8a4
mod_http_oauth2: Fix treatment of 'redirect_uri' parameter in code flow
It's optional and the one stored in the client registration should
really be used instead. RFC 6749 says an URI provided as parameter MUST
be validated against the stored one but does not say how.
Given that the client needs their secret to proceed, it seems fine to
leave this for later.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 02 Mar 2023 22:00:42 +0100 |
parent | 1182:547b3c05cc06 |
line wrap: on
line source
local jid_split = require "util.jid".split; local st = require "util.stanza"; local set = require "util.set"; local select = select; local blacklist = module:get_option_inherited_set("host_blacklist", {}); local function stanza_checker(attr) return function (event) local host = select(2, jid_split(event.stanza.attr[attr])); if blacklist:contains(host) then module:send(st.error_reply(event.stanza, "cancel", "not-allowed", "Communication with this domain is restricted")); return true; end end end check_incoming_stanza = stanza_checker("from"); check_outgoing_stanza = stanza_checker("to"); for stanza_type in set.new{"presence","message","iq"}:items() do for jid_type in set.new{"bare", "full", "host"}:items() do module:hook("pre-"..stanza_type.."/"..jid_type, check_outgoing_stanza, 500); module:hook(stanza_type.."/"..jid_type, check_incoming_stanza, 500); end end