Kim Alvefur <zash@zash.se> [Sun, 20 Oct 2019 16:47:20 +0200] rev 10348
doap: Copy longer description from README
Kim Alvefur <zash@zash.se> [Sun, 20 Oct 2019 16:37:04 +0200] rev 10347
Merge 0.11->trunk
Kim Alvefur <zash@zash.se> [Sun, 20 Oct 2019 14:54:57 +0200] rev 10346
MUC: Validate registration dataform more carefully
Kim Alvefur <zash@zash.se> [Sun, 20 Oct 2019 01:20:11 +0200] rev 10345
MUC: Don't advertise registration feature on host JID (fixes #1451)
There is currently no mention in XEP-0045 of how or where to advertise
support for registration.
Advertising on the host JID may be confusable with service-wide
registration, as implemented in ejabberd.
A common and sensible pattern in XMPP is that a feature is advertised on
the JID where the service is available.
Kim Alvefur <zash@zash.se> [Tue, 15 Oct 2019 23:38:29 +0200] rev 10344
mod_saslauth: Demote "no SASL mechanisms" error back to warning
This gets printed before TLS if c2s_require_encryption = false,
in which case it is just annoying.
Kim Alvefur <zash@zash.se> [Tue, 15 Oct 2019 22:05:51 +0200] rev 10343
mod_saslauth: Improve logging of why no SASL mechanisms were offered
Kim Alvefur <zash@zash.se> [Tue, 15 Oct 2019 21:58:10 +0200] rev 10342
mod_saslauth: Use the power of Set Theory to mange sets of SASL mechanisms
This makes sets of excluded mechanisms easily available for use later.
Kim Alvefur <zash@zash.se> [Tue, 15 Oct 2019 21:37:19 +0200] rev 10341
mod_saslauth: Log (debug) messages about channel binding
Kim Alvefur <zash@zash.se> [Tue, 15 Oct 2019 00:21:01 +0200] rev 10340
doc/doap: Claim support for XEP-0368 by way of legacy_ssl_ports
> Server support of XEP-0368 means having the ability to accept direct TLS connections.
This is what legacy_ssl_ports does. First trace of it seems to be 8458be0941e7
Kim Alvefur <zash@zash.se> [Tue, 15 Oct 2019 00:13:52 +0200] rev 10339
doc/doap: Claim support for XEP-0268 via mod_csi_simple
mod_csi_simple tries to follow the advice in XEP-0268.
Notably, since 7d78b24d8449 it also does this:
> If the server receives data, the phones radio is already on, therefore
> you should flush any pending data as soon as possible after receiving
> data from a client