From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Perale <thomas.perale@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 1/4] support/scripts/cve-check: add indication how to run
Date: Tue, 3 Mar 2026 23:23:49 +0100 [thread overview]
Message-ID: <20260303222352.95612-1-thomas.perale@mind.be> (raw)
Always run this script from the output of 'generate-cyclonedx'. Do not re-run
this script over an already analysed SBOMs.
Signed-off-by: Thomas Perale <thomas.perale@mind.be>
---
support/scripts/cve-check | 3 +++
1 file changed, 3 insertions(+)
diff --git a/support/scripts/cve-check b/support/scripts/cve-check
index ff14e4b238..2bb3524014 100755
--- a/support/scripts/cve-check
+++ b/support/scripts/cve-check
@@ -29,6 +29,9 @@ database.
The NVD database is cloned using a mirror of it and the content is compared
locally.
+
+Always run this script from the output of 'generate-cyclonedx'. Do not re-run
+this script over an already analysed SBOMs.
"""
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-03 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 22:23 Thomas Perale via buildroot [this message]
2026-03-03 22:23 ` [Buildroot] [PATCH 2/4] support/scripts/cve-check: remove 'bom-ref' for vulnerabilities Thomas Perale via buildroot
2026-03-03 22:23 ` [Buildroot] [PATCH 3/4] support/scripts/cve-check: fix vulnerabilities with different analysis Thomas Perale via buildroot
2026-03-03 22:23 ` [Buildroot] [PATCH 4/4] package/pkg-generic.mk: replicate IGNORE_CVES to host packages Thomas Perale via buildroot
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=20260303222352.95612-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
/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.