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.

---
labels:
- Stage-Alpha
summary: Limit which file transfer users can use
...

Introduction
------------

This module attempts to restrict use of non-whitelisted XEP-0065
proxies.

Configuration
-------------

Without any options, the module will restrict users to local [proxy65
components](https://prosody.im/doc/modules/mod_proxy65).

    -- additional proxies to allow
    allowed_streamhosts = { "proxy.eu.jabber.org" }

The module will add all local proxies to that list. To prevent it from
doing that, set

    allow_local_streamhosts = false