view mod_muc_rtbl/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 093c47ee2041
children 4c788f8be94e
line wrap: on
line source

---
summary: 
rockspec:
  dependencies:
  - mod_rtbl
labels:
- Stage-Alpha
...

This module subscribes to a real-time blocklist using pubsub (XEP-0060). As
entries are added and removed from the blocklist, it immediately updates a
local service-wide ban list.

# Configuring

Load this module on your existing MUC component like so:

```lua
Component "channels.example.com" "muc"
modules_enabled = {
	-- other modules etc
	"muc_rtbl";
}
```

Then you should configure one or more lists you want to subscribe to, supplying
full or partial URIs (the default node is 'muc_bans_sha256' if unspecified):

```lua
muc_rtbls = {
	"rtbl.example";
	-- Equivalent to above
	"xmpp:rtbl.example?;node=muc_bans_sha256";
}
```

If an unaffiliated JID matches an entry found in any of the configured RTBLs,
this module will block:

- Joins
- Group chat messages
- Private messages

from the JID that matched.

# Compatibility

Should work with Prosody >= 0.12.x

# Developers

## Protocol

This version of mod_muc_rtbl assumes that the pubsub node contains one item
per blocked JID. The item id should be the SHA256 hash of the JID to block.
The payload is not currently used, but it is recommend to use a XEP-0377
report element as the payload.