Mercurial > prosody-modules
view mod_muc_defaults/README.markdown @ 5285:8e1f1eb00b58
mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!)
Problem:
This was causing the key to become "<token>--cur" instead of the expected
"<token>-cur". As the same key was used by the code to both set and get, it
still worked.
Rationale for change:
Although it worked, it's unintended, inconsistent and messy. It increases the
chances of future bugs due to the unexpected format.
Side-effects of change:
Existing '--cur' entries will not be checked after this change, and therefore
existing FAST clients will fail to authenticate until they attempt password
auth and obtain a new FAST token.
Existing '--cur' entries in storage will not be cleaned up by this commit, but
this is considered a minor issue, and okay for the relatively few FAST
deployments.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Wed, 29 Mar 2023 16:12:15 +0100 |
parents | 22784f001b7f |
children | a1f8cc591b66 |
line wrap: on
line source
# mod_muc_defaults Creates MUCs with default configuration settings upon Prosody startup. ## Configuration Under your MUC component, add a `muc_defaults` option with the relevant settings. ``` Component "conference.example.org" "muc" modules_enabled = { "muc_defaults"; } muc_defaults = { { jid_node = "trollbox", affiliations = { admin = { "admin@example.org", "superuser@example.org" }, owner = { "owner@example.org" }, visitors = { "visitor@example.org" } }, config = { name = "General Chat", description = "Public chatroom with no particular topic", allow_member_invites = false, change_subject = false, history_length = 40, lang = "en", logging = true, members_only = false, moderated = false, persistent = true, public = true, public_jids = true } } }; ```