From: "akuster" <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [V2][PATCH] cve-check.bbclass: allow skiping non pbn
Date: Mon, 15 Feb 2021 22:42:54 +0000 [thread overview]
Message-ID: <20210215224254.2550264-1-akuster808@gmail.com> (raw)
I don't see the point in logging native, nativesdk etc.
The bottom line is the BPN has the issue.
Allow folks to filter out those other package name variations via
CVE_CHECK_MANIFEST_FILTER
Signed-off-by: Armin Kuster <akuster808@gmail.com>
--
[V2]
rename varible to CVE_CHECK_FILTER_BUILD_TOOLS
---
meta/classes/cve-check.bbclass | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 112ee3379d3..1bed815d8e4 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -59,6 +59,7 @@ CVE_CHECK_LAYER_EXCLUDELIST ??= ""
# Layers to be included
CVE_CHECK_LAYER_INCLUDELIST ??= ""
+CVE_CHECK_FILTER_BUILD_TOOLS ??="0"
# set to "alphabetical" for version using single alphabetical character as increament release
CVE_VERSION_SUFFIX ??= ""
@@ -96,6 +97,13 @@ python do_cve_check () {
"""
if os.path.exists(d.getVar("CVE_CHECK_DB_FILE")):
+ if d.getVar("CVE_CHECK_FILTER_BUILD_TOOLS") == "1":
+ # drop native, nativesdk, cross, etc
+ bpn = d.getVar("BPN")
+ pn = d.getVar("PN")
+ if bpn != pn:
+ return
+
try:
patched_cves = get_patches_cves(d)
except FileNotFoundError:
@@ -164,6 +172,7 @@ def get_patches_cves(d):
import re
pn = d.getVar("PN")
+
cve_match = re.compile("CVE:( CVE\-\d{4}\-\d+)+")
# Matches last CVE-1234-211432 in the file name, also if written
--
2.25.1
next reply other threads:[~2021-02-15 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 22:42 akuster [this message]
2021-02-16 8:37 ` [OE-core] [V2][PATCH] cve-check.bbclass: allow skiping non pbn Mikko Rapeli
2021-02-18 16:51 ` Ross Burton
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=20210215224254.2550264-1-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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