view mod_s2s_never_encrypt_blacklist/README.md @ 6319:04c3273cb81f

mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents fe081789f7b5
children
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