prosody-modules
527c747711f3
mod_s2s_never_encrypt_blacklist/README.markdown
Software / code / prosody-modules
File
mod_s2s_never_encrypt_blacklist/README.markdown @ 5705: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 |
| parent | 1803:4d73a1a6ba68 |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: | Stops prosody from including starttls into available features for specified remote servers. ... Details ------- Let's you stop Prosody from sending \<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'\> feature to choppy/buggy servers which therefore would fail to re-negotiate and use a secure stream. (e.g. [OpenFire 3.7.0](http://issues.igniterealtime.org/browse/OF-405)) Usage ----- Copy the plugin into your prosody's modules directory. And add it between your enabled modules into the global section (modules\_enabled). Then list each host as follow: tls_s2s_blacklist = { "host1.tld", "host2.tld", "host3.tld" } In the unfortunate case of OpenFire... you can add the Server's ip address directly as it may not send proper rfc6121 requests. tls_s2s_blacklist_ip = { "a.a.a.a", "b.b.b.b", "c.c.c.c" } Compatibility ------------- It's supposed to work with 0.7-0.8.x
