prosody-modules
4d6af8950016
mod_audit/README.md
Software / code / prosody-modules
File
mod_audit/README.md @ 5170:4d6af8950016
mod_muc_moderation: Derive role from reserved nickname if occupant
When using a different client to moderate than the one used to
participate in the chat, e.g. a command line tool like clix, there's no
occupant and no role to use in the permission check. Previously the
default role based on affiliation was used. Now if you are present in
the room using your reserved nick, the role you have there is used in
the permission check instead of the default affiliation-derived role.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 19 Feb 2023 18:17:37 +0100 |
| parent | 4932:530d116b7f68 |
| child | 5326:dc058fcc3fe3 |
line wrap: on
line source
--- summary: Audit Logging rockspec: {} ... This module provides infrastructure for audit logging inside Prosody. ## What is audit logging? Audit logs will contain security sensitive events, both for server-wide incidents as well as user-specific. This module, however, only provides the infrastructure for audit logging. It does not, by itself, generate such logs. For that, other modules, such as `mod_audit_auth` or `mod_audit_register` need to be loaded. ## A note on privacy Audit logging is intended to ensure the security of a system. As such, its contents are often at the same time highly sensitive (containing user names and IP addresses, for instance) and allowed to be stored under common privacy regulations. Before using these modules, you may want to ensure that you are legally allowed to store the data for the amount of time these modules will store it. Note that it is currently not possible to store different event types with different expiration times.
