Mercurial > prosody-modules
view mod_sasl2/README.md @ 5533:09311a8a3cfa
mod_firewall: spam-blocking.pfw: Remove requirement for invites to have no body
Some clients (e.g. Gajim) send a body, which I guess makes sense.
The bare JID sender check should already make it hard to bypass this (i.e.
a normal client putting muc#user into a normal chat message shouldn't bypass
the usual message filters).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 08 Jun 2023 12:20:34 +0100 |
parents | 5b77f4720bfe |
children | da942a3f3660 |
line wrap: on
line source
--- labels: - Stage-Beta summary: "XEP-0388: Extensible SASL Profile" --- Implementation of [XEP-0388: Extensible SASL Profile]. **Note: At the time of writing (Nov 2022) the version of the XEP implemented by this module is still working its way through the XSF standards process. See [PR #1214](https://github.com/xsf/xeps/pull/1214) for the current status.** ## Configuration This module honours the same configuration options as Prosody's existing [mod_saslauth](https://prosody.im/doc/modules/mod_saslauth). ## Developers mod_sasl2 provides some events you can hook to affect aspects of the authentication process: - `advertise-sasl-features` - `sasl2/c2s/success` - Priority 1000: Session marked as authenticated, success response created (`event.success`) - Priority -1000: Success response sent to client - Priority -1500: Updated <stream-features/> sent to client - `sasl2/c2s/failure` - `sasl2/c2s/error`