From: richard.purdie@linuxfoundation.org
To: akash.hadke@kpit.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [poky][master][PATCH 1/3] cve_check.py: Add new method get_ignored_cves
Date: Wed, 18 May 2022 11:33:42 +0100 [thread overview]
Message-ID: <e793362e2958aecec75daa66230558f7feb9add5.camel@linuxfoundation.org> (raw)
In-Reply-To: <13088.1652867175060959086@lists.openembedded.org>
On Wed, 2022-05-18 at 02:46 -0700, akash hadke via
lists.openembedded.org wrote:
> Hi Richard,
>
> I tried modifying the cve-check.bbclass but did not able to get the
> solution for disabling the NVD data, because when we inherit cve-
> check it executes the cve_check task that checks CVEs from NVD DB. So
> I am also not sure how to disable it hence I used the separate
> bbclass.
I guess the task dependencies are a bit of an issue there. There are
probably ways to make those configurable, it would just take a little
work.
I really do want to encourage us to work together on common cve tooling
rather than having several partial implementations so I can't take this
patch series.
Cheers,
Richard
next prev parent reply other threads:[~2022-05-18 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 14:36 [poky][master][PATCH 1/3] cve_check.py: Add new method get_ignored_cves Akash Hadke
2022-05-11 14:36 ` [poky][master][PATCH 2/3] cve-export.bbclass: Add a new class to get patched and ignored CVEs from the build Akash Hadke
2022-05-11 14:36 ` [poky][master][PATCH 3/3] cve_export.py: Add new selftest for cve-export.bbclass Akash Hadke
2022-05-17 9:12 ` [OE-core] [poky][master][PATCH 1/3] cve_check.py: Add new method get_ignored_cves Marta Rybczynska
2022-05-17 11:42 ` Akash Hadke
2022-05-17 13:33 ` Marta Rybczynska
2022-05-17 13:51 ` akash hadke
2022-05-17 14:19 ` [OE-core] " richard.purdie
2022-05-18 9:46 ` akash hadke
2022-05-18 10:33 ` richard.purdie [this message]
2022-05-18 11:58 ` [OE-core] " Marta Rybczynska
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=e793362e2958aecec75daa66230558f7feb9add5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akash.hadke@kpit.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