prosody-modules
f2363e6d9a64
mod_s2s_never_encrypt_blacklist/README.markdown
Software / code / prosody-modules
File
mod_s2s_never_encrypt_blacklist/README.markdown @ 5390:f2363e6d9a64
mod_http_oauth2: Advertise the currently supported id_token signing algorithm
This field is REQUIRED. The algorithm RS256 MUST be included, but isn't
because we don't implement it, as that would require implementing a pile
of additional cryptography and JWT stuff. Instead the id_token is
signed using the client secret, which allows verification by the client,
since it's a shared secret per OpenID Connect Core 1.0 § 10.1 under
Symmetric Signatures.
OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that
are not supported here, but that's okay because this is served from the
RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 30 Apr 2023 16:13:40 +0200 |
| 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
