Mercurial > prosody-modules
view mod_compat_dialback/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 | 41ebdb331b94 |
| children |
line wrap: on
line source
--- summary: Workaround for Dialback with some servers that violate RFC 6120 ... This module provides a workaround for servers that do not set the `to` attribute on stream headers, which is required per [RFC6120]: > ## 4.7.2. to > > For initial stream headers in both client-to-server and > server-to-server communication, the initiating entity MUST include the > 'to' attribute and MUST set its value to a domainpart that the > initiating entity knows or expects the receiving entity to service. As a side effect of [this issue](https://prosody.im/issues/issue/285), Prosody 0.10 will be unable to do [Dialback][xep220] with servers that don't follow this. # Known servers affected * Openfire 3.10.2 (and probably earlier versions)