Mercurial > prosody-modules
view mod_host_blacklist/mod_host_blacklist.lua @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | 547b3c05cc06 |
children |
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