Sat, 15 Jan 2022 09:09:24 +0100 mod_cron: Allow for a small amount of timer drift
Kim Alvefur <zash@zash.se> [Sat, 15 Jan 2022 09:09:24 +0100] rev 12190
mod_cron: Allow for a small amount of timer drift If the timer activates a bit early then a task might be just a few seconds short of being allowed to run. This would run such a task rather than wait another hour. The value 0.5% chosen so that a weekly task does not run an entire hour earlier than last time.
Fri, 14 Jan 2022 17:00:13 +0000 mod_storage_xep0227: Fix luacheck warnings
Matthew Wild <mwild1@gmail.com> [Fri, 14 Jan 2022 17:00:13 +0000] rev 12189
mod_storage_xep0227: Fix luacheck warnings
Fri, 14 Jan 2022 16:57:19 +0000 mod_storage_xep0227: Add API to iterate all stores of a user
Matthew Wild <mwild1@gmail.com> [Fri, 14 Jan 2022 16:57:19 +0000] rev 12188
mod_storage_xep0227: Add API to iterate all stores of a user
Fri, 14 Jan 2022 16:55:18 +0000 mod_storage_xep0227: Skip self-contacts on roster import
Matthew Wild <mwild1@gmail.com> [Fri, 14 Jan 2022 16:55:18 +0000] rev 12187
mod_storage_xep0227: Skip self-contacts on roster import
Thu, 13 Jan 2022 12:18:49 +0000 Added tag 0.11.12 for changeset 783056b4e448 0.11
Matthew Wild <mwild1@gmail.com> [Thu, 13 Jan 2022 12:18:49 +0000] rev 12186
Added tag 0.11.12 for changeset 783056b4e448
Mon, 10 Jan 2022 18:23:54 +0100 util.xml: Do not allow doctypes, comments or processing instructions 0.11 0.11.12
Jonas Schäfer <jonas@wielicki.name> [Mon, 10 Jan 2022 18:23:54 +0100] rev 12185
util.xml: Do not allow doctypes, comments or processing instructions Yes. This is as bad as it sounds. CVE pending. In Prosody itself, this only affects mod_websocket, which uses util.xml to parse the <open/> frame, thus allowing unauthenticated remote DoS using Billion Laughs. However, third-party modules using util.xml may also be affected by this. This commit installs handlers which disallow the use of doctype declarations and processing instructions without any escape hatch. It, by default, also introduces such a handler for comments, however, there is a way to enable comments nontheless. This is because util.xml is used to parse human-facing data, where comments are generally a desirable feature, and also because comments are generally harmless.
Mon, 10 Jan 2022 18:23:54 +0100 util.xml: Do not allow doctypes, comments or processing instructions
Jonas Schäfer <jonas@wielicki.name> [Mon, 10 Jan 2022 18:23:54 +0100] rev 12184
util.xml: Do not allow doctypes, comments or processing instructions Yes. This is as bad as it sounds. CVE pending. In Prosody itself, this only affects mod_websocket, which uses util.xml to parse the <open/> frame, thus allowing unauthenticated remote DoS using Billion Laughs. However, third-party modules using util.xml may also be affected by this. This commit installs handlers which disallow the use of doctype declarations and processing instructions without any escape hatch. It, by default, also introduces such a handler for comments, however, there is a way to enable comments nontheless. This is because util.xml is used to parse human-facing data, where comments are generally a desirable feature, and also because comments are generally harmless.
Tue, 11 Jan 2022 04:15:29 +0100 mod_http_file_share: Always measure total disk usage for statistics!
Kim Alvefur <zash@zash.se> [Tue, 11 Jan 2022 04:15:29 +0100] rev 12183
mod_http_file_share: Always measure total disk usage for statistics! Metrics available or not depending on configuration is weird, even tho it might be expensive to calculate and it's only really needed when there is a global quota. Default quota is set to infinity, which is essentially what it was. Reports NaN if there is an error, which should count as over the infinite default quota.
Tue, 11 Jan 2022 00:06:48 +0100 mod_bookmarks: Fix traceback on attempt to convert invalid bookmark
Kim Alvefur <zash@zash.se> [Tue, 11 Jan 2022 00:06:48 +0100] rev 12182
mod_bookmarks: Fix traceback on attempt to convert invalid bookmark Found by accidentally publishing {urn:xmpp:bookmarks:0}conference instead of :1 due to testing this earlier for the blocking. By the principle of garbage in, garbage out, just generate a bookmark from the item id / JID and carry on with a warning.
Mon, 10 Jan 2022 22:15:55 +0100 mod_bookmarks: Block publishing to older XEP-0402 v0.3.0 node
Kim Alvefur <zash@zash.se> [Mon, 10 Jan 2022 22:15:55 +0100] rev 12181
mod_bookmarks: Block publishing to older XEP-0402 v0.3.0 node Having both the :0 and :1 nodes would be especially awkward, since there is no upgrade path for this case. In theory, these should be rare since no clients should have been doing XEP-0402 unless mod_bookmarks(2) was enabled. This was guesstimated to be rare with most clients doing XEP-0048 with Private XML.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip