Mercurial > prosody-modules
view mod_firewall/scripts/spam-blocklists.pfw @ 5682:527c747711f3
mod_http_oauth2: Limit revocation to clients own tokens in strict mode
RFC 7009 section 2.1 states:
> The authorization server first validates the client credentials (in
> case of a confidential client) and then verifies whether the token was
> issued to the client making the revocation request. If this
> validation fails, the request is refused and the client is informed of
> the error by the authorization server as described below.
The first part was already covered (in strict mode). This adds the later
part using the hash of client_id recorded in 0860497152af
It still seems weird to me that revoking a leaked token should not be
allowed whoever might have discovered it, as that seems the responsible
thing to do.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 29 Oct 2023 11:30:49 +0100 |
| parents | d84757f9adcb |
| children |
line wrap: on
line source
# This script depends on spam-blocking.pfw also being loaded # Any traffic that is not explicitly blocked or allowed by other # rules will be checked against the JabberSPAM server blocklist %LIST blocklist: https://cdn.jsdelivr.net/gh/jabberspam/blacklist/blacklist.txt ::user/spam_handle_unknown_custom CHECK LIST: blocklist contains $<@from|host> BOUNCE=policy-violation (Your server is blocked due to spam) ::user/spam_check_muc_invite_custom # Check the server we received the invitation from CHECK LIST: blocklist contains $<@from|host> BOUNCE=policy-violation (Your server is blocked due to spam) # Check the inviter's JID against the blocklist, too CHECK LIST: blocklist contains $<{http://jabber.org/protocol/muc#user}x/invite@from|host> BOUNCE=policy-violation (Your server is blocked due to spam)