Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tcpdump: drop unneeded security patches
Date: Fri, 2 Oct 2015 09:37:03 -0300	[thread overview]
Message-ID: <560E7A6F.2060508@zacarias.com.ar> (raw)
In-Reply-To: <8eab1f5310d5dac8ab6e17bc5a0e4fdf5d3017ad.1443699935.git.baruch@tkos.co.il>

On 01/10/15 08:45, Baruch Siach wrote:

> Version 4.7.4 of tcpdump is not vulnerable to these issues according to:
>
>     https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-8767
>     https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-8768
>     https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-8769
>
> The tcpdump commit log seems to indicate that these issues were fixes in a
> different way in the following commits:
>
> CVE-2014-8767: 4038f83ebf654804829b258dde5e0a508c1c2003
> CVE-2014-8768: 9255c9b05b0a04b8d89739b3efcb9f393a617fe9
> CVE-2014-8769: 9ed7ddb48fd557dc993e73f22a50dda6cedf4df7
>
> Just drop these patches.
>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>

However i don't like upstream policy regarding vulns, there's no direct 
mention of these CVEs anywhere, it's very vague and hard to track.
Regards.

  reply	other threads:[~2015-10-02 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 11:45 [Buildroot] [PATCH] tcpdump: drop unneeded security patches Baruch Siach
2015-10-02 12:37 ` Gustavo Zacarias [this message]
2015-10-02 14:34   ` 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=560E7A6F.2060508@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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