public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] knot: Update to 3.0.5
Date: Sat, 27 Mar 2021 21:23:49 +0100	[thread overview]
Message-ID: <23501c01-5873-3cfd-9a94-9b0331fe3677@ipfire.org> (raw)
In-Reply-To: <20210327084725.1731-1-matthias.fischer@ipfire.org>

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

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> For details see:
> https://www.knot-dns.cz/2021-03-25-version-305.html
> 
> "Improvements:
> 
>         kdig: added support for TCP Fast Open on FreeBSD
>         keymgr: the SEP flag can be changed on already generated keys
>         Some documentation improvements
> 
> Bugfixes:
> 
>         knotd: journal contents can be considered malformed after changeset merge
>         knotd: broken detection of TCP Fast Open availability
>         knotd: zone restore can stuck in an infinite loop if zone configuration changed
>         knotd: failed zone backup makes control socket unavailable
>         knotd: zone not stored to journal after reload if difference-no-serial is enabled
>         knotd: old key is being used after an algorithm rollover with a shared policy #721
>         keymgr: keytag not recomputed upon key flag change
>         kdig: TCP not used if +fastopen is set

This one is interesting. :-)

>         mod-dnstap: the local address is empty
>         kzonecheck: missing letter lower-casing of the origin parameter
>         XDP mode wrongly detected on NetBSD
>         Failed to build knotd_stdio fuzzing utility"
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>  lfs/knot | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lfs/knot b/lfs/knot
> index 39940a358..bdf34b966 100644
> --- a/lfs/knot
> +++ b/lfs/knot
> @@ -1,7 +1,7 @@
>  ###############################################################################
>  #                                                                             #
>  # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2020  IPFire Team  <info(a)ipfire.org>                     #
> +# Copyright (C) 2007-2021  IPFire Team  <info(a)ipfire.org>                     #
>  #                                                                             #
>  # This program is free software: you can redistribute it and/or modify        #
>  # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
>  
>  include Config
>  
> -VER        = 3.0.4
> +VER        = 3.0.5
>  
>  THISAPP    = knot-$(VER)
>  DL_FILE    = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_MD5 = c0a546927ff50db153893de43758cb37
> +$(DL_FILE)_MD5 = 687d00586202bc0bbf0c76fa90921652
>  
>  install : $(TARGET)
>  
> 

      reply	other threads:[~2021-03-27 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27  8:47 Matthias Fischer
2021-03-27 20:23 ` Peter Müller [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=23501c01-5873-3cfd-9a94-9b0331fe3677@ipfire.org \
    --to=peter.mueller@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