From: Beniamin Sandu <beniaminsandu@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Beniamin Sandu <beniaminsandu@gmail.com>
Subject: [meta-oe][PATCH] libtorrent-rasterbar: fix CVE mapping
Date: Wed, 17 Apr 2024 23:32:19 +0100 [thread overview]
Message-ID: <20240417223219.893512-1-beniaminsandu@gmail.com> (raw)
Set CVE_PRODUCT for this recipe to fix the mapping,
as it was checking against the wrong recipe before.
Log from cve_check after change:
NOTE: libtorrent-rasterbar-2.0.10 is not vulnerable to CVE-2008-0646
NOTE: libtorrent-rasterbar-2.0.10 is not vulnerable to CVE-2009-1760
NOTE: libtorrent-rasterbar-2.0.10 is not vulnerable to CVE-2016-5301
NOTE: libtorrent-rasterbar-2.0.10 is not vulnerable to CVE-2016-7164
NOTE: libtorrent-rasterbar-2.0.10 is not vulnerable to CVE-2017-9847
Signed-off-by: Beniamin Sandu <beniaminsandu@gmail.com>
---
.../libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb b/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb
index 084e3c408..f2de1f468 100644
--- a/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb
+++ b/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb
@@ -17,6 +17,8 @@ S = "${WORKDIR}/git"
inherit cmake pkgconfig python3targetconfig
+CVE_PRODUCT = "libtorrent"
+
EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release"
PACKAGECONFIG ??= "python3"
--
2.34.1
reply other threads:[~2024-04-17 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240417223219.893512-1-beniaminsandu@gmail.com \
--to=beniaminsandu@gmail.com \
--cc=openembedded-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).