From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Cc: Matthias Fischer <matthias.fischer@ipfire.org>
Subject: [PATCH] knot: Update to 3.6.1
Date: Sat, 10 Oct 2026 00:13:18 +0200 [thread overview]
Message-ID: <20261009221321.1995938-1-matthias.fischer@ipfire.org> (raw)
For details see:
https://www.knot-dns.cz/2026-10-09-version-361.html
"Version 3.6.1
Friday, October 9, 2026
Features:
mod-ecs: new module for setting the ECS scope prefix length (Thanks to Branko Mijuskovic)
Improvements:
knotd: additional SOA consistency checks when processing incoming XFR
knotd: DDNS over 0-RTT QUIC/TLS is forbidden
knotd: new warning if difference(-no-serial) is enabled on a secondary zone
knotc: control blocking timeout is per full command, not per each zone
kdig: backward compatibility for +noidn as an alias for +noidnout
libknot: extra checks for malformed IPv4 and TCP packets in XDP filter (Thanks to Joshua Rogers)
src,tests: various compatibility fixes for SmartOS #980
doc: various improvements
Bugfixes:
knotd: missing synchronization between catalog reload and worker suspension
knotd: race condition between pausing/resuming events, zonedb update, and reload/conf-commit
knotd: non-consumed DoT 0-RTT early data can cause memory exhaustion (Thanks to Yuxiao Wu)
knotd: server can crash if NSEC3-enabled zone has empty NSEC3 chain (Thanks to Yuxiao Wu)
knotd: server sends 3 session tickets over DoQ
knotd: missing checks for malformed sentinel-related replies from Redis (Thanks to Joshua Rogers)
knotd: defective error handling during zone update (Thanks to Joshua Rogers)
knotd: defective TSIG MAC truncation processing (Thanks to Joshua Rogers)
knotd: zone update commit reads parent zone contents without RCU protection (Thanks to Joshua Rogers)
knotd: parent-check TTL can overflow KSK retirement delay (Thanks to Joshua Rogers)
knotd: missing DDNS queue synchronization during reload (Thanks to Joshua Rogers)
keymgr: validate-skr returns success for cryptographically invalid SKR signatures (Thanks to Joshua Rogers)
kdig: missing check for malformed EDNS/REPORTCHANNEL data (Thanks to Joshua Rogers)
libknot: defective output buffer handling in TCP over XDP
libknot: auto-generated TLS key file follows symlinks (Thanks to Joshua Rogers)
libknot: missing checks for malformed data in rrset-dump (Thanks to Joshua Rogers)
libzsanner: possible out-of-bounds write when parsing DELEG/DELEGPARAM dname (Thanks to Joshua Rogers)
redis: possible use-after-free when rrset index update fails (Thanks to Joshua Rogers)
redis: incorrect arity check for KNOT_BIN.UPD.LOAD (Thanks to Joshua Rogers)
redis: KNOT.ZONE.INFO crashes on nonexistent zone (Thanks to Joshua Rogers)
redis: update commit uses freed zset element buffer while applying updates (Thanks to Joshua Rogers)
python: receive_block() doesn't return data from the 'status' command"
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
---
lfs/knot | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/knot b/lfs/knot
index 97995b669..61f9ee0d9 100644
--- a/lfs/knot
+++ b/lfs/knot
@@ -24,7 +24,7 @@
include Config
-VER = 3.6.0
+VER = 3.6.1
THISAPP = knot-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 454d12deb35c91fd3c3e71cfd4021bd0d36fb39446e3cef41a47df3bbc0362950de1a21eb742d936dbce13a822891b313da335b8bb21026b88d4d985d8c763c0
+$(DL_FILE)_BLAKE2 = b052613f66af93ca041d77d73876361b980bb22f929a6330da38d5de213c29833ee875c1fcce89bef4047f55936fd743b302b3fee53f7b21cce60a2c219e8601
install : $(TARGET)
--
2.53.0
reply other threads:[~2026-10-09 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261009221321.1995938-1-matthias.fischer@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox