Software /
code /
prosody-modules
File
mod_sasl2/README.md @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
author | Jonas Schäfer <jonas@wielicki.name> |
---|---|
date | Tue, 21 Feb 2023 21:37:27 +0100 |
parent | 5089:5b77f4720bfe |
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`