From: Patrick Ohly <patrick.ohly@intel.com>
To: Mariano Lopez <mariano.lopez@linux.intel.com>
Cc: Scott Rifenbark <srifenbark@gmail.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"mariano.lopez@intel.com" <mariano.lopez@intel.com>
Subject: Re: cve-checker tool
Date: Fri, 28 Oct 2016 19:08:44 +0200 [thread overview]
Message-ID: <1477674524.13356.28.camel@intel.com> (raw)
In-Reply-To: <0cfba38f-d090-68d0-5c09-a20a5f5e1973@linux.intel.com>
On Fri, 2016-10-28 at 09:28 -0500, Mariano Lopez wrote:
>
> On 10/27/2016 06:03 AM, Sona Sarmadi wrote:
> >> Can this tool be used together with "meta-security-isafw" and get a fancy
> >> report?
>
> When I was working on this it was the transition to python3 so,
> meta-security-isafw didn't behave as expected.
It does now.
> To be honest I haven't
> checked again but it will be a good test. I'll try to do this during the
> weekend.
meta-security-isafw has its own support for generating CVE reports, for
example in the XMLunit format. Here's an example how Jenkins displays
that:
https://ostroproject.org/jenkins/view/Code-Analysis/job/code_isafw_reports/checker=cve,label=coordinator,machine=beaglebone/lastCompletedBuild/testReport/
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-10-28 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 11:03 cve-checker tool Sona Sarmadi
2016-10-28 2:34 ` Khem Raj
2016-10-28 9:03 ` Sona Sarmadi
2016-10-28 14:28 ` Mariano Lopez
2016-10-28 17:08 ` Patrick Ohly [this message]
2016-12-06 14:28 ` Sona Sarmadi
2016-12-06 14:41 ` Sona Sarmadi
2016-12-07 14:58 ` Mariano Lopez
2016-12-07 16:12 ` Burton, Ross
2016-12-07 16:14 ` Burton, Ross
-- strict thread matches above, loose matches on Subject: below --
2016-10-27 8:56 Sona Sarmadi
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=1477674524.13356.28.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=mariano.lopez@intel.com \
--cc=mariano.lopez@linux.intel.com \
--cc=srifenbark@gmail.com \
--cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.