Mercurial > prosody-modules
view mod_audit/README.md @ 5627:3a5cf8d80089
mod_http_oauth2: Tweak method of centering the UI
The percentage here was relative to the viewport width, which on some
very wide screens may put the UI slightly outside of the view, requiring
scrolling to see.
By using a unit relative to the height of the viewport, this is avoided
and should work better. But no guarantees, it's still possible to resize
the browser or adjust font sizes so that the UI goes out of view.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 31 Jul 2023 07:28:09 +0200 |
parents | dc058fcc3fe3 |
children | 561503e0c0f1 |
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. ## Viewing the log You can view the log using prosodyctl. This works even when Prosody is not running. For example, to view the full audit log for example.com: ```shell prosodyctl mod_audit example.com ``` To view only host-wide events (those not attached to a specific user account), use the `--global` option (or use `--no-global` to hide such events): ```shell prosodyctl mod_audit --global example.com ``` To narrow results to a specific user, specify their JID: ```shell prosodyctl mod_audit user@example.com ```