Kim Alvefur <zash@zash.se> [Sat, 31 Oct 2020 00:33:29 +0100] rev 11662
net.server_epoll: Ensure timeout after closing
This should make sure that if there's data left to be written when
closing a connection, there's also a timeout so that it doesn't wait
forever.
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 15:11:53 +0200] rev 11661
core.loggingmanager: Disable pretty printing when not connected to a tty
Things can behave unexpectedly when fed ANSI escape codes.
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 15:11:07 +0200] rev 11660
util.pposix: Bind isatty(3)
Useful for disabling certain behavior, ANSI colors etc when not
connected to a terminal.
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 02:33:15 +0200] rev 11659
util.prosodyctl.check: Normalize away trailing dot in some messages too
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 01:33:53 +0200] rev 11658
util.prosodyctl.check: Normalize potential to form without trailing '.'
In some cases you might end up with both 'xmpp.example.com' and
'xmpp.example.com.', which are the same thing so no point in doing the
same checks twice.
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 01:32:04 +0200] rev 11657
util.prosodyctl.check: Point out if A/AAAA exists despite disabled IPvX
Clients would try to connect and receive an error or timeout, increasing
the time it takes to establish a connection. Probably not what you want.
If you really want IPv6 or IPv4 disabled, best remove the A or AAAA record.
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 01:29:47 +0200] rev 11656
util.prosodyctl.check: Warn if both use_ipv4 and use_ipv6 are set to false
Why would you do this?!
Kim Alvefur <zash@zash.se> [Sun, 04 Jul 2021 01:23:35 +0200] rev 11655
util.prosodyctl.check: Silence IP protocol mismatches when disabled
If you set 'use_ipv4 = false' then you probably don't care much for the
host not resolving to the IPv4 address, and same with 'use_ipv6'.
Kim Alvefur <zash@zash.se> [Sat, 03 Jul 2021 17:28:07 +0200] rev 11654
Merge 0.11->trunk
Kim Alvefur <zash@zash.se> [Sat, 03 Jul 2021 03:27:57 +0200] rev 11653
util.ip: Fix netmask for link-local address range
This may have mistakenly caused link-local addresses to be considered
global. May have caused mod_s2s and prosodyctl check dns to behave
incorrectly on networks using link-local IPv4 addresses. By my
guesstimate, these are extremely rare. Probably minimal impact beyond
a bit longer to establish s2s and some possible confusion from
prosodyctl check dns results.
Ref RFC 3927