All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libnids: drop LIBNIDS_IGNORE_CVES
Date: Sun, 23 May 2021 15:29:38 +0200	[thread overview]
Message-ID: <20210523132938.1520248-2-fontaine.fabrice@gmail.com> (raw)
In-Reply-To: <20210523132938.1520248-1-fontaine.fabrice@gmail.com>

NVD database has been updated:
https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&seach_type=all&query=cpe:2.3:a:libnids_project:libnids:1.24:*:*:*:*:*:*:*

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@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 4a9138b80e..3e36838c40 100644
--- a/package/libnids/libnids.mk
+++ b/package/libnids/libnids.mk
@@ -13,10 +13,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.30.2

  reply	other threads:[~2021-05-23 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 13:29 [Buildroot] [PATCH 1/2] package/libnids: add LIBNIDS_CPE_ID_VENDOR Fabrice Fontaine
2021-05-23 13:29 ` Fabrice Fontaine [this message]
2021-05-23 18:03   ` [Buildroot] [PATCH 2/2] package/libnids: drop LIBNIDS_IGNORE_CVES Yann E. MORIN
2021-06-08  7:13   ` Peter Korsgaard
2021-05-23 17:58 ` [Buildroot] [PATCH 1/2] package/libnids: add LIBNIDS_CPE_ID_VENDOR Yann E. MORIN
2021-06-08  7:10 ` 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=20210523132938.1520248-2-fontaine.fabrice@gmail.com \
    --to=fontaine.fabrice@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.