From: mariano.lopez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Add initial capability to check CVEs for recipes
Date: Wed, 24 Feb 2016 15:27:05 +0000 [thread overview]
Message-ID: <cover.1456327117.git.mariano.lopez@linux.intel.com> (raw)
From: Mariano Lopez <mariano.lopez@linux.intel.com>
This series add the cve-check-tool recipe, a tool used to identify
potentially vulnerable software through version matching. It will
check if a vulnerability has been addressed by a patch.
Also add the new cve-check class that will add a task for all recipes
to check for CVEs using cve-check-tool. This tool can be used by recipe,
image (will generate an image report in deploy dir), and with "world"
and "universe"
To run it just inherit the class and enter:
bitbake -c cve_check <recipe>
The following changes since commit 23056103c949b498c23b47579e8dd57ce78e6ed9:
uclibc: Do not use immediate expansion operator (2016-02-22 20:42:48 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib mariano/bug7515
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mariano/bug7515
Mariano Lopez (3):
cve-check-tool: Add recipe
cve-check-tool patch to allow select dir for the db
cve-check.bbclass: Add class
meta/classes/cve-check.bbclass | 229 +++++++++++++++++++++
.../change_logic_cve_get_file_parent.patch | 45 ++++
.../cve-check-tool/cve-check-tool_5.6.bb | 61 ++++++
3 files changed, 335 insertions(+)
create mode 100644 meta/classes/cve-check.bbclass
create mode 100644 meta/recipes-devtools/cve-check-tool/cve-check-tool/change_logic_cve_get_file_parent.patch
create mode 100644 meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.bb
--
2.6.2
next reply other threads:[~2016-02-24 23:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 15:27 mariano.lopez [this message]
2016-02-24 15:27 ` [PATCH 1/3] cve-check-tool: Add recipe mariano.lopez
2016-02-25 0:44 ` Burton, Ross
2016-02-24 15:27 ` [PATCH 2/3] cve-check-tool patch to allow select dir for the db mariano.lopez
2016-02-25 13:33 ` Burton, Ross
2016-02-25 14:46 ` Mariano Lopez
2016-02-24 15:27 ` [PATCH 3/3] cve-check.bbclass: Add class mariano.lopez
2016-02-29 14:50 ` Burton, Ross
2016-02-29 20:06 ` Mariano Lopez
2016-02-25 12:14 ` [PATCH 0/3] Add initial capability to check CVEs for recipes Mikko.Rapeli
2016-02-25 12:29 ` Mikko.Rapeli
2016-02-25 13:27 ` Mikko.Rapeli
2016-02-25 14:09 ` Mikko.Rapeli
2016-02-26 8:14 ` Mikko.Rapeli
2016-02-26 14:48 ` Mariano Lopez
2016-02-26 14:56 ` Mikko.Rapeli
2016-02-26 14:57 ` Mikko.Rapeli
2016-02-26 15:38 ` Mariano Lopez
2016-02-29 14:17 ` Burton, Ross
2016-02-29 14:19 ` Mikko.Rapeli
2016-03-01 15:15 ` Mariano Lopez
2016-03-02 6:32 ` Mikko.Rapeli
[not found] ` <56CF2B81.4080500@mvista.com>
2016-02-25 17:22 ` Mariano Lopez
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=cover.1456327117.git.mariano.lopez@linux.intel.com \
--to=mariano.lopez@linux.intel.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