Mercurial > prosody-modules
view mod_s2s_smacks_timeout/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 | 78368d2865dd |
| children |
line wrap: on
line source
--- labels: - Stage-Obsolete --- # Introduction ::: {.alert .alert-warning} This behavior has now been merged into [mod_s2s][doc:modules:mod_s2s] in trunk and is therefore obsolete when used with trunk. It can still be used with Prosody 0.12 to get this behavior. ::: This module closes s2s connections when [mod_smacks][doc:modules:mod_smacks] reports that a connection has not received a timely acknowledgement as requested, indicating that the connection is broken or the remote server is not responding. With the connection closed, the next stanza to be directed to that server will trigger Prosody to establish a new connection, instead of queueing it on the potentially broken connection. This should prevent messages from being stuck in a queue for a potentially long time before being bounced back to the sender as delivery failure reports. Normally the amount of time it takes for a broken connection to time out is determined by TCP. If this is deemed sensible behavior then it will likely be merged into Prosody itself somewhere.