All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Sona Sarmadi <sona.sarmadi@enea.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Scott Rifenbark <srifenbark@gmail.com>,
	"mariano.lopez@intel.com" <mariano.lopez@intel.com>
Subject: Re: cve-checker tool
Date: Thu, 27 Oct 2016 19:34:04 -0700	[thread overview]
Message-ID: <D98FD381-BC63-421E-AD53-8A808C02CCDF@gmail.com> (raw)
In-Reply-To: <3230301C09DEF9499B442BBE162C5E48ABEA948F@SESTOEX04.enea.se>

[-- Attachment #1: Type: text/plain, Size: 2100 bytes --]


> On Oct 27, 2016, at 4:03 AM, Sona Sarmadi <sona.sarmadi@enea.com> wrote:
> 
> 
> 
>> -----Original Message-----
>> From: Sona Sarmadi
>> Sent: den 27 oktober 2016 10:57
>> To: Scott Rifenbark <srifenbark@gmail.com>; 'mariano.lopez@intel.com'
>> <mariano.lopez@intel.com>; yocto@yoctoproject.org
>> Subject: cve-checker tool
>> 
>> Hi guys,
>> 
>> I have some questions regarding cve-check tool. I don't find anything
>> about this tool in Yocto
>> 2.2 release, dose documentation mention this tool and how to use it?
>> 
>> Is this tool planned to be integrated with daily build so the Yocto project
>> can detect Not addressed CVEs automatically?
>> 
>> Mariano:
>> Does this tool look at CVE tag inside the recipe as well or only checks the
>> package version?
>> 
>> Can this tool be used together with "meta-security-isafw" and get a fancy
>> report?
> 
> There are some useful info in the cve-check.bbclass:
> 
> #In order to use this class just inherit the class in the
> # local.conf file and it will add the cve_check task for
> # every recipe. The task can be used per recipe, per image,
> # or using the special cases "world" and "universe". The
> # cve_check task will print a warning for every unpatched
> # CVE found and generate a file in the recipe WORKDIR/cve
> # directory. If an image is build it will generate a report
> # in DEPLOY_DIR_IMAGE for all the packages used.
> 
> I see following logs are generated:
> ./unzip/1_6.0-r5/cve/cve.log
> ./gnutls/3.5.3-r0/cve/cve.log
> ./glibc/2.24-r0/cve/cve.log
> ./glibc-initial/2.24-r0/cve/cve.log
> ./foomatic-filters/4.0.17-r1/cve/cve.log
> ./bzip2/1.0.6-r5/cve/cve.log
> ./libxml2/2.9.4-r0/cve/cve.log
> ./perl/5.22.1-r0/cve/cve.log
> ./expat/2.2.0-r0/cve/cve.log
> ./flex/2.6.0-r0/cve/cve.log

perhaps you can add this info to "How Do I”
section in wiki here https://wiki.yoctoproject.org/wiki/How_do_I

> 
> //Sona
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2016-10-28  2:34 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 [this message]
2016-10-28  9:03   ` Sona Sarmadi
2016-10-28 14:28 ` Mariano Lopez
2016-10-28 17:08   ` Patrick Ohly
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=D98FD381-BC63-421E-AD53-8A808C02CCDF@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=mariano.lopez@intel.com \
    --cc=sona.sarmadi@enea.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.