Kim Alvefur <zash@zash.se> [Sun, 08 Dec 2019 17:48:37 +0100] rev 10498
util.x509: Fix recording of CommonNames in get_identities
Don't worry, this function is not used by anything yet, this isn't a
security issue. It'll be used by Prosody to pick the correct certificate
for itself in the future.
The `names` multitable is a collection of (name, service) pairs but it
put them in the wrong order here.
Kim Alvefur <zash@zash.se> [Sun, 08 Dec 2019 17:00:45 +0100] rev 10497
util.error: Write down some thoughts in comments
Kim Alvefur <zash@zash.se> [Sun, 08 Dec 2019 14:26:32 +0100] rev 10496
net.server_epoll: Use monotonic time for scheduling
Timer API of passing wallclock time remains
Kim Alvefur <zash@zash.se> [Sun, 08 Dec 2019 14:20:56 +0100] rev 10495
net.server_epoll: Change timer rescheduling method to match util.timer
Relative to current time instead of absolute time, in preparation for
switching to monotonic time.
Kim Alvefur <zash@zash.se> [Sun, 08 Dec 2019 13:40:42 +0100] rev 10494
net.server_epoll: Remove unused function for adding timer at absolute time
This won't make sense if we switch to monotonic time
Kim Alvefur <zash@zash.se> [Sun, 08 Dec 2019 13:38:48 +0100] rev 10493
mod_admin_telnet: Avoid using LuaSocket for timestamps
Using util.time will make it easier to move away from LuaSocket if we
ever wanted to do that.
Kim Alvefur <zash@zash.se> [Sat, 07 Dec 2019 22:55:51 +0100] rev 10492
mod_saslauth: Set a nicer bounce error explaining SASL EXTERNAL failures
Better than the previous string concatenation of SASL failure condition
and optional text sent by the remote server.
Would be nice to have a text per condition, other than the probably most
common 'not-authorized'.
Kim Alvefur <zash@zash.se> [Sat, 07 Dec 2019 22:51:43 +0100] rev 10491
mod_saslauth: Collect SASL EXTERNAL failures into an util.error object
Will be easier than that concatenated string to extract info out of for
use elsewhere.
Kim Alvefur <zash@zash.se> [Sat, 07 Dec 2019 19:05:10 +0100] rev 10490
net.server_epoll: Add debug logging for delayed reading
In :onreadable, if there is still buffered incoming data after reading
from the socket (as indicated by the :dirty method, usually because
LuaSocket has an 8k buffer that's full but it read a smaller amount),
another attempt to read is scheduled via this :pausefor method. This is
also called from some other places where it would be pointless to read
because there shouldn't be any data.
In the delayed read case, this should report that the socket is "dirty".
If it reports that the socket is "clean" then the question is where
the buffer contents went?
If this doesn't get logged after the scheduled time (0.000001s by
default) then this would suggests a problem with timer or scheduling.
Kim Alvefur <zash@zash.se> [Sat, 07 Dec 2019 17:39:29 +0100] rev 10489
net.connect: Mention RFC 6724 regression
Default Address Selection algorithm is not applied, resulting in a
strong bias towards IPv4.