From: "Ross Burton" <ross.burton@intel.com>
To: Anders Montonen <Anders.Montonen@iki.fi>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] cve-checker name collisions
Date: Fri, 24 Jan 2020 10:54:09 +0000 [thread overview]
Message-ID: <866d4701-b299-dcc8-4541-4da98daeb8ed@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2001241057320.4667@lakka.kapsi.fi>
On 24/01/2020 09:02, Anders Montonen wrote:
> Hi,
>
> What's the best way for handling name collisions when using the
> cve-checker tool? For example, there's a ton of Adobe Flex
> vulnerabilities that are reported against the Flex lexical analyzer
> generator tool. Whitelisting the individual CVEs would be one option,
> but the list is pretty long.
Set CVE_PRODUCT, if you use a colon then you can set the vendor too.
This specific instance is already fixed in oe-core master:
# Not Apache Flex, or Adobe Flex, or IBM Flex.
CVE_PRODUCT = "flex_project:flex"
Ross
next prev parent reply other threads:[~2020-01-24 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 9:02 cve-checker name collisions Anders Montonen
2020-01-24 9:41 ` [yocto] " Mikko Rapeli
2020-01-24 10:54 ` Ross Burton [this message]
2020-01-27 8:16 ` Anders Montonen
2020-01-27 9:04 ` 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=866d4701-b299-dcc8-4541-4da98daeb8ed@intel.com \
--to=ross.burton@intel.com \
--cc=Anders.Montonen@iki.fi \
--cc=yocto@lists.yoctoproject.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