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.5.6
Date: Tue, 21 Jul 2026 17:36:01 +0200 [thread overview]
Message-ID: <20260721153609.3343018-1-matthias.fischer@ipfire.org> (raw)
For details see:
https://www.knot-dns.cz/2026-07-20-version-356.html
"Version 3.5.6
Monday, July 20, 2026
Improvements:
knotd: new log message when accepting a control client fails
knotd: new log message when UDP or TCP worker initialization fails
knotd: improved log message when loading an expired zone
knotd: more verbose log messages for DDNS forwarding
knotd: disabled 0-RTT when forwarding DDNS updates over QUIC
utils: configuration detection considers an empty database directory as unused
libknot: added support for EDE code 33 (Negative Trust Anchor) (Thanks to Babak Farrokhi)
libs: upgraded embedded libngtcp2 to 1.24.0
doc: various improvements
Bugfixes:
knotd: server crashes when evaluating an ACL rule with 'cert-hostname' set
knotd: failed to start with 'listen-tls' and 'tcp-reuseport' enabled
knotd: missing proper mutex (de)initialization for controlling access to some zone properties
knotd: server crashes when it fails to load a QUIC/TLS key
knotd: zone control unset does not respect the TTL value of the removed record
knotd: incomplete configuration check for conflicting ACL settings
libknot: XDP frame limit does not correctly consider the MTU limit
libknot: QUIC connection not closed on handshake failure (Thanks to Vendemiat) !1886
knot-exporter: uncaught exception when connecting to knotd that is not running #974"
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 a68619134..24c083ea1 100644
--- a/lfs/knot
+++ b/lfs/knot
@@ -24,7 +24,7 @@
include Config
-VER = 3.5.5
+VER = 3.5.6
THISAPP = knot-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 5ee478109a26e3b163da169e7e22a03780727528f84953e399f25670d48392b6b407388c38b152bc90399f517b70676168735c1aba4028326237b92cdf904938
+$(DL_FILE)_BLAKE2 = f03a2da9390e89bd7955505d3f59ca54689e2183b1ea0f82efbf5abedd71f16902c6d09f77adceaedd29573d52135c168441dbf46721709b370269220b68f49b
install : $(TARGET)
--
2.53.0
reply other threads:[~2026-07-21 15:36 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=20260721153609.3343018-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