From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] knot: Update to 3.0.7
Date: Sun, 20 Jun 2021 20:26:46 +0200 [thread overview]
Message-ID: <c0496d13-5daa-2707-d74d-5b3c47164816@ipfire.org> (raw)
In-Reply-To: <20210620121520.1351-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
On 20/06/2021 14:15, Matthias Fischer wrote:
> For details see:
> https://www.knot-dns.cz/2021-06-16-version-307.html
>
> Features:
>
> knotd: new configuration policy option for CDS digest algorithm setting #738
> keymgr: new command for primary SOA serial manipulation in on-secondary signing mode
>
> Improvements:
>
> knotd: improved algorithm rollover to shorten the last step of old RRSIG publication
>
> Bugfixes:
>
> knotd: zone is flushed upon server start, despite DNSSEC signing is up-to-date
> knotd: wildcard nonexistence is proved on empty-non-terminal query
> knotd: redundant wildcard proof for non-authoritative data in a reply
> knotd: missing wildcard proofs in a wildcard-cname loop reply
> knotd: incorrectly synthesized CNAME owner from a wildcard record #715
> knotd: zone-in-journal changeset ignores journal-max-usage limit #736
> knotd: incorrect processing of zone-in-journal changeset with SOA serial 0
> knotd: broken initialization of processing workers if SO_REUSEPORT(_LB) not available
> kjournalprint: reported journal usage is incorrect #736
> keymgr: cannot parse algorithm name ed448 #739
> keymgr: default key size not set properly
> kdig: failed to process huge DoH responses
> libknot/probe: some corner-case bugs
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/knot | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/knot b/lfs/knot
> index ec6ec4deb..7e8bbc202 100644
> --- a/lfs/knot
> +++ b/lfs/knot
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3.0.6
> +VER = 3.0.7
>
> THISAPP = knot-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 0d8aaa8e5214623c12123c67b5f2c460
> +$(DL_FILE)_MD5 = a7ac9e92989184437a45578d0e23990a
>
> install : $(TARGET)
>
prev parent reply other threads:[~2021-06-20 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 12:15 Matthias Fischer
2021-06-20 18:26 ` Adolf Belka [this message]
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=c0496d13-5daa-2707-d74d-5b3c47164816@ipfire.org \
--to=adolf.belka@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