Sun, 25 Jul 2021 14:01:45 +0200 mod_pubsub: Normalize 'publisher' JID
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 14:01:45 +0200] rev 11721
mod_pubsub: Normalize 'publisher' JID All the XEP-0060 examples have the publisher attribute set to a bare JID, but the text does allow it to be the full JID. Since mod_pubsub is more likely used for open nodes that anyone can subscribe to it makes sense to not leak the full JIDs. This is also disabled by defaults. In mod_pep on the other hand it might make sense to have the full JID since that data is more likely to be broadcast to contacts which are already somewhat trusted.
Sun, 25 Jul 2021 13:52:52 +0200 scansion tests: Enable 'expose_publisher' since we test for it
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 13:52:52 +0200] rev 11720
scansion tests: Enable 'expose_publisher' since we test for it
Sun, 25 Jul 2021 13:52:27 +0200 mod_pubsub: Respect 'expose publisher' setting in item retrieval
Kim Alvefur <zash@zash.se> [Sun, 25 Jul 2021 13:52:27 +0200] rev 11719
mod_pubsub: Respect 'expose publisher' setting in item retrieval
Wed, 01 May 2019 22:33:22 +0200 mod_pubsub: Fix inclusion of publisher (fixes #1399)
Kim Alvefur <zash@zash.se> [Wed, 01 May 2019 22:33:22 +0200] rev 11718
mod_pubsub: Fix inclusion of publisher (fixes #1399)
Fri, 23 Jul 2021 17:13:06 +0200 Merge 0.11->trunk
Kim Alvefur <zash@zash.se> [Fri, 23 Jul 2021 17:13:06 +0200] rev 11717
Merge 0.11->trunk
Thu, 22 Jul 2021 17:18:39 +0200 MUC: Fix logic for access to affiliation lists 0.11 0.11.10
Kim Alvefur <zash@zash.se> [Thu, 22 Jul 2021 17:18:39 +0200] rev 11716
MUC: Fix logic for access to affiliation lists Fixes https://prosody.im/security/advisory_20210722/ Backs out 4d7b925652d9
Mon, 19 Jul 2021 17:07:59 +0200 MUC: Skip adding to history when it's set to zero
Kim Alvefur <zash@zash.se> [Mon, 19 Jul 2021 17:07:59 +0200] rev 11715
MUC: Skip adding to history when it's set to zero Optimizes away all the processing on every message in case the end-result is zero history.
Sun, 18 Jul 2021 23:25:45 +0200 net.resolvers.service: Only do DANE with secure SRV records
Kim Alvefur <zash@zash.se> [Sun, 18 Jul 2021 23:25:45 +0200] rev 11714
net.resolvers.service: Only do DANE with secure SRV records If this seems backwards, that' because it is but the API isn't really designed to easily pass along details from each resolution step onto the next.
Sun, 18 Jul 2021 22:46:57 +0200 core.certmanager: Support 'use_dane' setting to enable DANE support
Kim Alvefur <zash@zash.se> [Sun, 18 Jul 2021 22:46:57 +0200] rev 11713
core.certmanager: Support 'use_dane' setting to enable DANE support Removes the need to enable DANE with two separate settings. Previously you had to also set `ssl = { dane = true }` to activate DANE support in LuaSec and OpenSSL.
Sun, 18 Jul 2021 21:57:24 +0200 Revert 926d53af9a7a: Restore DANE support
Kim Alvefur <zash@zash.se> [Sun, 18 Jul 2021 21:57:24 +0200] rev 11712
Revert 926d53af9a7a: Restore DANE support Previous commit adds a workaround, so this doesn't mutate global state anymore, only per-connection 'extra' state as originally intended.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip