From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <ross.burton@arm.com>,
"openembedded-core" <openembedded-core@lists.openembedded.org>,
"openembedded-architecture"
<openembedded-architecture@lists.openembedded.org>
Subject: Re: [OE-core] Future of CVE scanning in Yocto
Date: Tue, 11 Mar 2025 12:00:01 +0100 [thread overview]
Message-ID: <D8DDV08P0OY1.2DFW4R71EYW40@bootlin.com> (raw)
In-Reply-To: <7D6E419E-A7AE-4324-966C-3552C586E452@arm.com>
Hi Ross,
On Fri Mar 7, 2025 at 3:36 PM CET, Ross Burton via lists.openembedded.org wrote:
[...]
> tl;dr: I propose:
> - For the upcoming (April 2025) release we should add to the release notes that we’re aware that NVD is struggling, this is what our CVE tooling is based on, and we’re working on a solution for the October 2025 release.
I've tried to summarize and add the known issue to the release note here:
https://lists.yoctoproject.org/g/docs/message/6530
Is there a bug associated to this? I could add it to the release note for people
to track the progress on this.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-03-11 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 14:36 Future of CVE scanning in Yocto Ross Burton
2025-03-10 15:37 ` [Openembedded-architecture] " Marta Rybczynska
2025-03-11 11:00 ` Antonin Godard [this message]
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=D8DDV08P0OY1.2DFW4R71EYW40@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox