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] unbound: Update to 1.10.1
Date: Tue, 19 May 2020 12:50:46 +0000	[thread overview]
Message-ID: <d37bc126-e7e7-78ec-e610-9d09ae17834d@ipfire.org> (raw)
In-Reply-To: <20200519121758.1623-1-matthias.fischer@ipfire.org>

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

That was quick, I just read the security announcement at the oss-security mailing list. :-)

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


> For details see:
> https://lists.nlnetlabs.nl/pipermail/unbound-users/2020-May/006833.html
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>  config/rootfiles/common/unbound | 2 +-
>  lfs/unbound                     | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/config/rootfiles/common/unbound b/config/rootfiles/common/unbound
> index 945b08507..cfa8d8ae5 100644
> --- a/config/rootfiles/common/unbound
> +++ b/config/rootfiles/common/unbound
> @@ -11,7 +11,7 @@ etc/unbound/unbound.conf
>  #usr/lib/libunbound.la
>  #usr/lib/libunbound.so
>  usr/lib/libunbound.so.8
> -usr/lib/libunbound.so.8.1.7
> +usr/lib/libunbound.so.8.1.8
>  #usr/lib/pkgconfig/libunbound.pc
>  usr/sbin/unbound
>  usr/sbin/unbound-anchor
> diff --git a/lfs/unbound b/lfs/unbound
> index 14c1bca5b..c119d6b2d 100644
> --- a/lfs/unbound
> +++ b/lfs/unbound
> @@ -1,7 +1,7 @@
>  ###############################################################################
>  #                                                                             #
>  # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>                     #
> +# Copyright (C) 2007-2020  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        = 1.10.0
> +VER        = 1.10.1
>  
>  THISAPP    = unbound-$(VER)
>  DL_FILE    = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_MD5 = 0754392baee77c18fd8295b5e51e6fd8
> +$(DL_FILE)_MD5 = 48f8ee02d0d92603a8d7f4fda7152da0
>  
>  install : $(TARGET)
>  
> 

  reply	other threads:[~2020-05-19 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 12:17 Matthias Fischer
2020-05-19 12:50 ` Peter Müller [this message]
2020-05-19 12:59   ` 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=d37bc126-e7e7-78ec-e610-9d09ae17834d@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