Mercurial > prosody-modules
view mod_storage_muc_log/README.markdown @ 4651:8231774f5bfd
mod_cloud_notify_encrypted: Ensure body substring remains valid UTF-8
The `body:sub()` call risks splitting the string in the middle of a
multi-byte UTF-8 sequence. This should have been caught by util.stanza
validation, but that would have caused some havoc, at the very least causing
the notification to not be sent.
There have been no reports of this happening. Likely because this module
isn't widely deployed among users with languages that use many longer UTF-8
sequences.
The util.encodings.utf8.valid() function is O(n) where only the last
sequence really needs to be checked, but it's in C and expected to be fast.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 22 Aug 2021 13:22:59 +0200 |
parents | 058844edcaaf |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - ArchiveStorage summary: 'Storage module using mod\_muc\_log data with new stanza archive API' --- Introduction ============ [mod\_muc\_log] provided logging of chatrooms running on the server to Prosody's data store. This module gives access to this data using the 0.10+ stanza archive API, allowing legacy log data to be used with [mod\_mam\_muc] and [mod\_http\_muc\_log]. Details ======= Replace [mod\_muc\_log] and [mod\_muc\_log\_http] in your config with ``` {.lua} Component "conference.example.org" "muc" modules_enabled = { -- "muc_log"; -- functionality replaced by mod_mam_muc + mod_storage_muc_log "mam_muc"; -- Does logging to storage backend configured below -- "muc_log_http"; -- Replaced by the mod_http_muc_log "http_muc_log"; } storage = { muc_log = "muc_log"; } ``` Compatibility ============= version status --------- --------------- 0.9 unknown 0.10 works 0.11 does not work