From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Jeffrey Pautler <jeffrey.pautler@ni.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [PATCH] bolt: disable CVE checking for this recipe
Date: Mon, 2 Oct 2023 12:22:55 +0300 [thread overview]
Message-ID: <ZRqL7yT0ME00CakU@nuoska> (raw)
In-Reply-To: <20230929170731.749414-1-jeffrey.pautler@ni.com>
Hi,
On Fri, Sep 29, 2023 at 12:07:31PM -0500, Jeffrey Pautler wrote:
> This bolt product does not currently have an entry in the CVE database.
> However, the default cve-check logic that maps recipes to products in
> the CVE database is incorrectly matching this package to a different
> bolt product made by bolt-cms. As a result, CVE checking incorrectly
> reports CVEs for that product for this package.
>
> Signed-off-by: Jeffrey Pautler <jeffrey.pautler@ni.com>
> ---
> meta-oe/recipes-bsp/bolt/bolt_0.9.5.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta-oe/recipes-bsp/bolt/bolt_0.9.5.bb b/meta-oe/recipes-bsp/bolt/bolt_0.9.5.bb
> index b6ad6337c..583cc6378 100644
> --- a/meta-oe/recipes-bsp/bolt/bolt_0.9.5.bb
> +++ b/meta-oe/recipes-bsp/bolt/bolt_0.9.5.bb
> @@ -12,6 +12,8 @@ SRCREV = "5a8a5866a847561566499847d46a97c612b4e6dd"
>
> S = "${WORKDIR}/git"
>
> +CVE_CHECK_SKIP_RECIPE = "${PN}"
I think this is wrong and dangerous for anyone who in the future tries to use
cve checker for this recipe. Instead, set the CVE product with vendor correctly
so that other products/vendors don't mix the results? Hopefully any new CVEs
in the future will set the same vendor and product.
Cheers,
-Mikko
> inherit cmake pkgconfig meson features_check
>
> FILES:${PN} += "${datadir}/dbus-1/* \
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#105252): https://lists.openembedded.org/g/openembedded-devel/message/105252
> Mute This Topic: https://lists.openembedded.org/mt/101662068/7159507
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [mikko.rapeli@linaro.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2023-10-02 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 17:07 [PATCH] bolt: disable CVE checking for this recipe Jeffrey Pautler
2023-10-02 9:22 ` Mikko Rapeli [this message]
2023-10-02 15:53 ` [oe] " Alex Stewart
2023-10-02 16:06 ` Khem Raj
2023-10-02 18:14 ` Marta Rybczynska
2023-10-03 4:54 ` Mikko Rapeli
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=ZRqL7yT0ME00CakU@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=jeffrey.pautler@ni.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 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.