Mercurial > prosody-modules
view mod_limits_exception/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 | 12a2989c7cc1 |
| children |
line wrap: on
line source
--- labels: - Stage-Obsolete summary: Allow specified JIDs to bypass rate limits --- This module allows you to configure a list of JIDs that should be allowed to bypass rate limit restrictions. It is designed for Prosody 0.11.x. Prosody 0.12.x supports this feature natively. ## Configuration First, enable this module by adding `"limits_exception"` to your `modules_enabled` list. Next, configure a list of JIDs to exclude from rate limiting: ``` unlimited_jids = { "user1@example.com", "user2@example.net" } ``` ## Compatibility Made for Prosody 0.11.x only. Using this module with Prosody trunk/0.12 may cause unexpected behaviour.
