Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: emil.kronborg@protonmail.com, openembedded-core@lists.openembedded.org
Cc: rasmus.villemoes@prevas.dk
Subject: Re: [OE-core] [PATCH v2] python3-pytest: add CVE_PRODUCT
Date: Thu, 21 Mar 2024 12:13:51 +0000	[thread overview]
Message-ID: <e84b352028020f21749dc07088c22c2d1d10bd38.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240320160910.231632-1-emil.kronborg@protonmail.com>

On Wed, 2024-03-20 at 16:09 +0000, Emil Kronborg via
lists.openembedded.org wrote:
> For some reason, the CVE product is just called py and not pytest in
> the
> NIST NVD database. Since the database only accept keywords with at
> least
> 3 characters, the CVE vendor must also be specified.
> 
> Signed-off-by: Emil Kronborg <emil.kronborg@protonmail.com>
> ---
> Changes in v2:
> - I forgot to sign the first version.
> 
>  meta/recipes-devtools/python/python3-pytest_8.0.2.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> b/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> index 57e979e909c3..080b89ebdd5e 100644
> --- a/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> +++ b/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> @@ -5,6 +5,8 @@ DESCRIPTION = "The pytest framework makes it easy to
> write small tests, yet scal
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM =
> "file://LICENSE;md5=bd27e41b6550fe0fc45356d1d81ee37c"
>  
> +CVE_PRODUCT = "pytest:py"
> +
>  SRC_URI[sha256sum] =
> "d4051d623a2e0b7e51960ba963193b09ce6daeb9759a451844a21e4ddedfc1bd"
>  
>  DEPENDS += "python3-setuptools-scm-native"

I worry this is a misfiled CPE rather than general statement that
they'd always use this for pytest CVEs. We might want to talk to them
about tweaking it to be consistent? I'm certainly unsure about taking
this patch as it might mask future issues?

Cheers,

Richard


  reply	other threads:[~2024-03-21 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 16:09 [PATCH v2] python3-pytest: add CVE_PRODUCT Emil Kronborg
2024-03-21 12:13 ` Richard Purdie [this message]
2024-03-23 16:06   ` [OE-core] " Emil Kronborg
2024-03-21 17:10 ` Ross Burton
2024-03-23 16:09   ` Emil Kronborg

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=e84b352028020f21749dc07088c22c2d1d10bd38.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=emil.kronborg@protonmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rasmus.villemoes@prevas.dk \
    /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