public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] knot: Update to 3.0.6
Date: Tue, 25 May 2021 10:49:07 +0100	[thread overview]
Message-ID: <8F524EC6-9444-4007-B29D-31421131576A@ipfire.org> (raw)
In-Reply-To: <20210522133231.3801-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2647 bytes --]

Hello Matthias,

Good to hear from you again :)

This patch does not apply, because we have 3.0.4 in next and not .5.

I looked on the mailing list but could not find a patch for .5.

Could you please rebase this on next and resubmit?

Best,
-Michael

> On 22 May 2021, at 14:32, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> For details see:
> https://www.knot-dns.cz/2021-05-12-version-306.html
> 
> "
> Features:
> 
>        mod-probe: new module for simple traffic logging (Python API not yet included)
> 
> Improvements:
> 
>        keymgr: new mode for listing zones with at least one key stored
>        keymgr: the pregenerate command accepts optional timestamp-from parameter
>        kzonecheck: accept '-' as substitution for standard input #727
>        knotd: print an error when unable to change owner of a logging file
>        knotd: new warning log if no interface is configured
>        knotd: new signing policy check for NSEC3 iterations higher than 20
>        knotd: don't allow backup to/restore from the DB storage directory
>        Various code (mostly zone backup/restore), tests, and documentation improvements
> 
> Bugfixes:
> 
>        knotd: secondary fails to load zone file if HTTPS or SVCB record is present #725
>        knotd: (KSK roll-over) new KSK is not signing DNSKEY long enough before DS submission
>        knotd: (KSK roll-over) old KSK uselessly published after roll-over finished
>        knotd: malformed address in TCP-related logs when listening on a UNIX socket
>        knotd: server responds FORMERR instead of BADTIME if TSIG signed time is zero #730
>        modules: incorrect local and remote addresses in the XDP mode
>        modules: failed to read configuration from a section without identifiers
>        mod-synthrecord: queries on synthesized empty-non-terminals not answered with NODATA
>        keymgr: confusing error if del-all-old command fails"
> 
> 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 bdf34b966..ec6ec4deb 100644
> --- a/lfs/knot
> +++ b/lfs/knot
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 3.0.5
> +VER        = 3.0.6
> 
> THISAPP    = knot-$(VER)
> DL_FILE    = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 687d00586202bc0bbf0c76fa90921652
> +$(DL_FILE)_MD5 = 0d8aaa8e5214623c12123c67b5f2c460
> 
> install : $(TARGET)
> 
> -- 
> 2.18.0
> 


  parent reply	other threads:[~2021-05-25  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 13:32 Matthias Fischer
2021-05-22 16:34 ` Peter Müller
2021-05-25  9:49 ` Michael Tremer [this message]
2021-05-25 15:31   ` Matthias Fischer
2021-05-25 15:37 Matthias Fischer

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=8F524EC6-9444-4007-B29D-31421131576A@ipfire.org \
    --to=michael.tremer@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