From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpdump: security bump to 4.9.1
Date: Wed, 26 Jul 2017 11:41:04 +0200 [thread overview]
Message-ID: <20170726094104.GL26551@argentina> (raw)
Fixes CVE-2017-11108/Fix bounds checking for STP
Changelog: http://www.tcpdump.org/tcpdump-changes.txt
Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
---
Could someone please double-check the hash? I checked the PGP key but do not
have the full trust mechanism so cannot be sure that the server public key is
valid.
package/tcpdump/tcpdump.hash | 2 +-
package/tcpdump/tcpdump.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/tcpdump/tcpdump.hash b/package/tcpdump/tcpdump.hash
index 966db1f3aa..ecd02275fe 100644
--- a/package/tcpdump/tcpdump.hash
+++ b/package/tcpdump/tcpdump.hash
@@ -1,2 +1,2 @@
# Locally calculated after checking pgp signature
-sha256 eae98121cbb1c9adbedd9a777bf2eae9fa1c1c676424a54740311c8abcee5a5e tcpdump-4.9.0.tar.gz
+sha256 f9448cf4deb2049acf713655c736342662e652ef40dbe0a8f6f8d5b9ce5bd8f3 tcpdump-4.9.1.tar.gz
diff --git a/package/tcpdump/tcpdump.mk b/package/tcpdump/tcpdump.mk
index 0e779a53c3..8349748ceb 100644
--- a/package/tcpdump/tcpdump.mk
+++ b/package/tcpdump/tcpdump.mk
@@ -4,7 +4,7 @@
#
################################################################################
-TCPDUMP_VERSION = 4.9.0
+TCPDUMP_VERSION = 4.9.1
TCPDUMP_SITE = http://www.tcpdump.org/release
TCPDUMP_LICENSE = BSD-3-Clause
TCPDUMP_LICENSE_FILES = LICENSE
--
2.13.0
next reply other threads:[~2017-07-26 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 9:41 Thomas De Schampheleire [this message]
2017-07-26 14:34 ` [Buildroot] [PATCH] tcpdump: security bump to 4.9.1 Baruch Siach
2017-07-26 14:53 ` Peter Korsgaard
2017-07-26 20:53 ` Peter Korsgaard
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=20170726094104.GL26551@argentina \
--to=thomas.de_schampheleire@nokia.com \
--cc=buildroot@busybox.net \
/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