Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-03-01 Thread Mikko.Rapeli
On Tue, Mar 01, 2016 at 09:15:37AM -0600, Mariano Lopez wrote: > > > On 02/29/2016 08:19 AM, mikko.rap...@bmw.de wrote: > >On Mon, Feb 29, 2016 at 02:17:26PM +, Burton, Ross wrote: > >>On 26 February 2016 at 08:14, wrote: > >> > >>>17:45:37 *** 0013:with open(patch_file, "r") as f:

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-03-01 Thread Mariano Lopez
On 02/29/2016 08:19 AM, mikko.rap...@bmw.de wrote: On Mon, Feb 29, 2016 at 02:17:26PM +, Burton, Ross wrote: On 26 February 2016 at 08:14, wrote: 17:45:37 *** 0013:with open(patch_file, "r") as f: 17:45:37 0014:patch_text = f.read() 17:45:37 0015: 17:45:37

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-29 Thread Mikko.Rapeli
On Mon, Feb 29, 2016 at 02:17:26PM +, Burton, Ross wrote: > On 26 February 2016 at 08:14, wrote: > > > 17:45:37 *** 0013:with open(patch_file, "r") as f: > > 17:45:37 0014:patch_text = f.read() > > 17:45:37 0015: > > 17:45:37 0016:# Search for the "

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-29 Thread Burton, Ross
On 26 February 2016 at 08:14, wrote: > 17:45:37 *** 0013:with open(patch_file, "r") as f: > 17:45:37 0014:patch_text = f.read() > 17:45:37 0015: > 17:45:37 0016:# Search for the "CVE: " line > 17:45:37 0017:match = cve_match.search(patch_te

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-26 Thread Mariano Lopez
On 02/26/2016 08:57 AM, mikko.rap...@bmw.de wrote: On Fri, Feb 26, 2016 at 03:56:24PM +0100, Mikko Rapeli wrote: On Fri, Feb 26, 2016 at 08:48:47AM -0600, Mariano Lopez wrote: On 02/26/2016 02:14 AM, mikko.rap...@bmw.de wrote: Hi, On my developer machine the cve-check ran ok for dizzy but on

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-26 Thread Mikko.Rapeli
On Fri, Feb 26, 2016 at 03:56:24PM +0100, Mikko Rapeli wrote: > On Fri, Feb 26, 2016 at 08:48:47AM -0600, Mariano Lopez wrote: > > On 02/26/2016 02:14 AM, mikko.rap...@bmw.de wrote: > > >Hi, > > > > > >On my developer machine the cve-check ran ok for dizzy but on build server > > >with sstate-cache

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-26 Thread Mikko.Rapeli
On Fri, Feb 26, 2016 at 08:48:47AM -0600, Mariano Lopez wrote: > On 02/26/2016 02:14 AM, mikko.rap...@bmw.de wrote: > >Hi, > > > >On my developer machine the cve-check ran ok for dizzy but on build server > >with sstate-cache and rmwork enabled it failed with what looks like a race > >condition whe

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-26 Thread Mariano Lopez
On 02/26/2016 02:14 AM, mikko.rap...@bmw.de wrote: Hi, On my developer machine the cve-check ran ok for dizzy but on build server with sstate-cache and rmwork enabled it failed with what looks like a race condition when scanning the patch files: 17:45:36 ERROR: Error executing a python function

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-26 Thread Mikko.Rapeli
Hi, On my developer machine the cve-check ran ok for dizzy but on build server with sstate-cache and rmwork enabled it failed with what looks like a race condition when scanning the patch files: 17:45:36 ERROR: Error executing a python function in /home/builder/src/base/poky/meta/recipes-extende

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-25 Thread Mariano Lopez
On 02/25/2016 10:27 AM, akuster wrote: So my questions in the bugs go unanswered. If you don't ever intend on responding just say so, I do appreciate honestly. I then know where I stand. - armin Sorry, for not answered the bug earlier, to be honest I hadn't seen your comment earlier. I

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-25 Thread Mikko.Rapeli
For openssh there must be some bugs or tunings needed to match the version numbers used in CVE to ones in yocto. openssh-6.6p1 has zero matches with the check but I think there are several: downloads/CVE_CHECK$ grep openssh *xml| grep 6\.6\:p1 nvdcve-2.0-2016.xml: nvdcve-2.0-2016.xml:

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-25 Thread Mikko.Rapeli
On Thu, Feb 25, 2016 at 01:29:13PM +0100, Mikko Rapeli wrote: > On Thu, Feb 25, 2016 at 01:14:21PM +0100, Mikko Rapeli wrote: > > On Wed, Feb 24, 2016 at 03:27:05PM +, mariano.lo...@linux.intel.com > > wrote: > > > From: Mariano Lopez > > > > > > This series add the cve-check-tool recipe, a

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-25 Thread Mikko.Rapeli
On Thu, Feb 25, 2016 at 01:14:21PM +0100, Mikko Rapeli wrote: > On Wed, Feb 24, 2016 at 03:27:05PM +, mariano.lo...@linux.intel.com wrote: > > From: Mariano Lopez > > > > This series add the cve-check-tool recipe, a tool used to identify > > potentially vulnerable software through version mat

Re: [OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-25 Thread Mikko.Rapeli
On Wed, Feb 24, 2016 at 03:27:05PM +, mariano.lo...@linux.intel.com wrote: > From: Mariano Lopez > > 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.

[OE-core] [PATCH 0/3] Add initial capability to check CVEs for recipes

2016-02-24 Thread mariano . lopez
From: Mariano Lopez 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