From: mariano.lopez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv4 0/2] Add initial capability to check CVEs for recipes
Date: Wed, 24 Aug 2016 18:58:33 +0000 [thread overview]
Message-ID: <cover.1472060412.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,
mage (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>
Changes in v2:
- Set the explicit dependency of cve-check-tool-native:do_populate_cve_db
in the cve-check class
- Squashed patch 2 into patch 1
Changes in v3:
- Support for python3
- Add check for BB_NO_NETWORK
Changes in v4:
- Support for GCC 6 adding -Wno-error=pedantic to CFLAGS
- Support for musl thanks to patch from Khem
- Tweaks when building the the CVE database
- Fix license
The following changes since commit a81b326933d15f08e06780f92d8dc0d4efb3cd23:
combo-layer: python3: fix UnicodeDecodeError (2016-08-24 13:58:28 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib mariano/bug7515v5
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mariano/bug7515v5
Mariano Lopez (2):
cve-check-tool: Add recipe
cve-check.bbclass: Add class
meta/classes/cve-check.bbclass | 267 +++++++++++++++++++++
.../cve-check-tool/cve-check-tool_5.6.4.bb | 59 +++++
.../check-for-malloc_trim-before-using-it.patch | 51 ++++
3 files changed, 377 insertions(+)
create mode 100644 meta/classes/cve-check.bbclass
create mode 100644 meta/recipes-devtools/cve-check-tool/cve-check-tool_5.6.4.bb
create mode 100644 meta/recipes-devtools/cve-check-tool/files/check-for-malloc_trim-before-using-it.patch
--
2.6.6
next reply other threads:[~2016-08-25 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 18:58 mariano.lopez [this message]
2016-08-24 18:58 ` [PATCHv4 1/2] cve-check-tool: Add recipe mariano.lopez
2016-08-25 14:28 ` Burton, Ross
2016-08-25 16:57 ` Khem Raj
2016-08-25 17:12 ` Burton, Ross
2016-08-25 13:01 ` mariano.lopez
2016-08-24 18:58 ` [PATCHv4 2/2] cve-check.bbclass: Add class 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.1472060412.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