Mercurial > prosody-modules
view mod_storage_muconference_readonly/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 | 9754eedbc4d1 |
children |
line wrap: on
line source
--- labels: - 'Type-Storage' - 'Stage-Alpha' summary: MU-Conference SQL Read-only Storage Module ... Introduction ============ This is a storage backend using MU-Conference’s SQL storage. It depends on [LuaDBI][doc:depends#luadbi] This module only works in read-only, and was made to be used by [mod_migrate] to migrate from MU-Conference’s SQL storage. You may need to convert your 'rooms' and 'rooms\_lists' tables to utf8mb4 before running that script, in order not to end up with mojibake. Note that MySQL doesn’t support having more than 191 characters in the jid field in this case, so you may have to change the table schema as well. Configuration ============= Copy the module to the prosody modules/plugins directory. In Prosody's configuration file, set: storage = "muconference_readonly" MUConferenceSQL options are the same as the [SQL ones][doc:modules:mod_storage_sql#usage]. Compatibility ============= ------- --------------------------- trunk Works 0.10 Untested, but should work 0.9 Does not work ------- ---------------------------