Software /
code /
prosody-modules
File
mod_s2s_never_encrypt_blacklist/README.markdown @ 4941:e7b9bc629ecc
mod_rest: Add special handling to catch MAM results from remote hosts
Makes MAM queries to remote hosts works.
As the comment says, MAM results from users' local archives or local
MUCs are returned via origin.send() which is provided in the event and
thus already worked. Results from remote hosts go via normal stanza
routing and events, which need this extra handling to catch.
This pattern of iq-set, message+, iq-result is generally limited to MAM.
Closest similar thing might be MUC join, but to really handle that you
would need the webhook callback mechanism.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 16 May 2022 19:47:09 +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