What steps will reproduce the problem?:
Do not allow non-admins to mark a multi-user room as public by adding the following to the prosody config file:
modules_enabled = { "muc_config_restrict" }
muc_config_restricted = {
"muc#roomconfig_publicroom"; -- Prevent non-admins from changing whether rooms are members-only
}
What is the expected output?
Non-admins should not be able to mark a multi-user chat/room as publicly listed.
What do you see instead?
Non-admins are able to mark a multi-user chat/room as publicly listed, and it works.
What version of the product are you using? On what operating system?
0.11.4-1 on Ubuntu 20.04 LTS
Please provide any additional information below.
-
Albert
on
Update: I am now using version 0.11.11-1~focal1 on Ubuntu 20.04 LTS
Zash
on
Thanks for the report.
Given the age of the module and the massive changes to MUC in 0.11, it's very likely that it would need to be updated to work again.
The compatibility table in the documentation implies as much, what it refers to as "trunk" would be approximately 0.10 back then, still predating the 0.11 MUC changes.
Since this is a community module, you are encouraged to try fixing it yourself. ;)
What steps will reproduce the problem?: Do not allow non-admins to mark a multi-user room as public by adding the following to the prosody config file: modules_enabled = { "muc_config_restrict" } muc_config_restricted = { "muc#roomconfig_publicroom"; -- Prevent non-admins from changing whether rooms are members-only } What is the expected output? Non-admins should not be able to mark a multi-user chat/room as publicly listed. What do you see instead? Non-admins are able to mark a multi-user chat/room as publicly listed, and it works. What version of the product are you using? On what operating system? 0.11.4-1 on Ubuntu 20.04 LTS Please provide any additional information below. -
Update: I am now using version 0.11.11-1~focal1 on Ubuntu 20.04 LTS
Thanks for the report. Given the age of the module and the massive changes to MUC in 0.11, it's very likely that it would need to be updated to work again. The compatibility table in the documentation implies as much, what it refers to as "trunk" would be approximately 0.10 back then, still predating the 0.11 MUC changes. Since this is a community module, you are encouraged to try fixing it yourself. ;)
Changes