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.

# This is a simple ruleset to block all traffic from servers
# on the JabberSPAM blocklist. Even traffic from existing user
# contacts will be blocked.
#
# Example config (make sure "firewall" is in modules_enabled):
#
#   firewall_scripts = { "module:scripts/jabberspam-simple-blocklist.pfw" }
#
# For a more advanced ruleset, consider using spam-blocking.pfw
# and spam-blocklists.pfw.

%LIST blocklist: https://cdn.jsdelivr.net/gh/jabberspam/blacklist/blacklist.txt

::deliver

CHECK LIST: blocklist contains $<@from|host>
BOUNCE=policy-violation (Your server is blocked due to spam)