public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c72bbdb029e24c366d75ecafea6a6c333b574ed2
Date: Mon, 13 Feb 2017 13:08:57 +0000	[thread overview]
Message-ID: <20170213130858.3A3CD1078E80@git01.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  c72bbdb029e24c366d75ecafea6a6c333b574ed2 (commit)
      from  c008a5a00e963796a11ea6e1f59f0e801fa1a088 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c72bbdb029e24c366d75ecafea6a6c333b574ed2
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date:   Fri Feb 10 22:44:58 2017 +0100

    bind: Update to 9.11.0-P3
    
    For details see:
    https://ftp.isc.org/isc/bind9/9.11.0-P3/RELEASE-NOTES-bind-9.11.0-P3.html
    
    "BIND 9.11.0-P3 addresses the security issue described in CVE-2017-3135,
    and fixes a regression introduced in a prior security release.
    
    BIND 9.11.0-P2 addresses the security issues described in CVE-2016-9131,
    CVE-2016-9147, CVE-2016-9444 and CVE-2016-9778.
    
    BIND 9.11.0-P1 addresses the security issue described in CVE-2016-8864.
    
    ...
    
    Security Fixes
    
    If a server is configured with a response policy zone (RPZ) that rewrites an
    answer with local data, and is also configured for DNS64 address mapping, a
    NULL pointer can be read triggering a server crash. This flaw is disclosed in
    CVE-2017-3135. [RT #44434]
    
    A coding error in the nxdomain-redirect feature could lead to an assertion
    failure if the redirection namespace was served from a local authoritative
    data source such as a local zone or a DLZ instead of via recursive lookup.
    This flaw is disclosed in CVE-2016-9778. [RT #43837]
    
    named could mishandle authority sections with missing RRSIGs, triggering an
    assertion failure. This flaw is disclosed in CVE-2016-9444. [RT #43632]
    
    named mishandled some responses where covering RRSIG records were returned
    without the requested data, resulting in an assertion failure. This flaw is
    disclosed in CVE-2016-9147.
    [RT #43548]
    
    named incorrectly tried to cache TKEY records which could trigger an assertion
    failure when there was a class mismatch. This flaw is disclosed in CVE-2016-9131.
    [RT #43522]
    
    It was possible to trigger assertions when processing responses containing answers
    of type DNAME. This flaw is disclosed in CVE-2016-8864. [RT #43465]"
    
    Best,
    Matthias
    
    Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/bind | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/lfs/bind b/lfs/bind
index d25c2df..e178219 100644
--- a/lfs/bind
+++ b/lfs/bind
@@ -25,7 +25,7 @@
 
 include Config
 
-VER        = 9.11.0-P2
+VER        = 9.11.0-P3
 
 THISAPP    = bind-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = b8ccec541de18ac2716e7a8268baaaba
+$(DL_FILE)_MD5 = 311787a0a69345a1f1cf7869b0266bf0
 
 install : $(TARGET)
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2017-02-13 13:08 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=20170213130858.3A3CD1078E80@git01.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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