Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: guillaume.bressaix at gmail.com <guillaume.bressaix@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libnids: NVD database has been updated
Date: Tue, 21 Jul 2020 20:05:55 +0200	[thread overview]
Message-ID: <20200721180555.31453-1-guillaume.bressaix@gmail.com> (raw)

From: "Guillaume W. Bres" <guillaume.bressaix@gmail.com>

Thanks to Matthew W. & Thomas, the NVD database has been updated
and CVE-2010-0751 is now declared fixed, see
https://security-tracker.debian.org/tracker/CVE-2010-0751

Signed-off-by: Guillaume W. Bres <guillaume.bressaix@gmail.com>
---
 package/libnids/libnids.mk | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/package/libnids/libnids.mk b/package/libnids/libnids.mk
index fb3df318b4..4a67215242 100644
--- a/package/libnids/libnids.mk
+++ b/package/libnids/libnids.mk
@@ -12,10 +12,6 @@ LIBNIDS_INSTALL_STAGING = YES
 LIBNIDS_DEPENDENCIES = host-pkgconf libpcap
 LIBNIDS_AUTORECONF = YES
 
-# CVE-2010-0751 was fixed in libnids v1.24 but the NVD database is not
-# aware of the fix, ignore it until this is updated
-LIBNIDS_IGNORE_CVES += CVE-2010-0751
-
 # disable libnet if not available
 # Tests in configure.in expect --with-libnet=$build_dir
 # not an installation patch like in our context.
-- 
2.20.1

             reply	other threads:[~2020-07-21 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 18:05 guillaume.bressaix at gmail.com [this message]
2020-07-21 18:43 ` [Buildroot] [PATCH 1/1] package/libnids: NVD database has been updated Thomas Petazzoni
2020-07-21 20:08   ` Matthew Weber
2020-07-22  7:32     ` Guillaume Bres
2020-07-30 18:01       ` Matthew Weber
2020-08-05 16:18         ` Matthew Weber
2020-08-05 19:48           ` Thomas Petazzoni
2020-08-05 21:43             ` [Buildroot] [External] " Matthew Weber

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=20200721180555.31453-1-guillaume.bressaix@gmail.com \
    --to=guillaume.bressaix@gmail.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