From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: Ross Burton <ross.burton@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] cve-check: allow recipes to override the product name
Date: Wed, 7 Dec 2016 11:05:39 -0600 [thread overview]
Message-ID: <f224566f-576b-acad-e23b-ee401d9dc2ac@linux.intel.com> (raw)
In-Reply-To: <1481129438-28306-1-git-send-email-ross.burton@intel.com>
On 07/12/16 10:50, Ross Burton wrote:
> Add a new variable CVE_PRODUCT for the product name to look up in the NVD
> database. Default this to BPN, but allow recipes such as tiff (which is libtiff
> in NVD) to override it.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
>
I like the idea to be able to override the name that cve-check-tool
checks. The only drawback would be the burden of adding these to needed
recipes. This is still better to have to guess the correct name, or to
check PROVIDES or RPROVIDES, there are just too much corner cases. So
this solution has my approval.
prev parent reply other threads:[~2016-12-07 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 16:50 [PATCH 1/3] cve-check: allow recipes to override the product name Ross Burton
2016-12-07 16:50 ` [PATCH 2/3] tiff: set CVE_PRODUCT Ross Burton
2016-12-07 16:50 ` [PATCH 3/3] curl: " Ross Burton
2016-12-07 17:05 ` Mariano Lopez [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=f224566f-576b-acad-e23b-ee401d9dc2ac@linux.intel.com \
--to=mariano.lopez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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