From: Adrian Bunk <bunk@stusta.de>
To: Pierre Le Magourou <lemagoup@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] cve-update-db: New recipe to update CVE database
Date: Wed, 19 Jun 2019 23:21:49 +0300 [thread overview]
Message-ID: <20190619202149.GA12516@localhost> (raw)
In-Reply-To: <20190619135940.18544-1-lemagoup@gmail.com>
Not sure which of the changes is responsible, but this is new:
WARNING: flex-native-2.6.0-r0 do_cve_check: Found unpatched CVE (CVE-2015-1773)
https://nvd.nist.gov/vuln/detail/CVE-2015-1773
Note that the flex tool is completely unrelated to Apache Flex.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-06-19 20:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 13:59 [PATCH 1/4] cve-update-db: New recipe to update CVE database Pierre Le Magourou
2019-06-19 13:59 ` [PATCH 2/4] cve-check: Remove dependency to cve-check-tool-native Pierre Le Magourou
2019-06-19 14:59 ` Burton, Ross
2019-06-19 15:58 ` Pierre Le Magourou
2019-06-19 13:59 ` [PATCH 3/4] cve-check: Manage CVE_PRODUCT with more than one name Pierre Le Magourou
2019-06-19 13:59 ` [PATCH 4/4] cve-check: Consider CVE that affects versions with less than operator Pierre Le Magourou
2019-06-19 20:21 ` Adrian Bunk [this message]
2019-06-20 9:36 ` [PATCH 1/4] cve-update-db: New recipe to update CVE database Pierre Le Magourou
2019-06-21 11:03 ` Mikko.Rapeli
2019-06-21 11:42 ` Alexander Kanavin
2019-06-21 11:48 ` Mikko.Rapeli
2019-06-21 12:03 ` Alexander Kanavin
2019-06-21 12:15 ` Mikko.Rapeli
2019-06-21 12:29 ` Burton, Ross
2019-06-21 13:01 ` Mikko.Rapeli
2019-06-25 8:48 ` Pierre Le Magourou
2019-06-25 12:54 ` Burton, Ross
2019-06-24 8:32 ` Pierre Le Magourou
2019-06-24 9:46 ` Burton, Ross
2019-06-27 7:31 ` Richard Purdie
2019-06-27 9:10 ` Pierre Le Magourou
2019-07-09 23:58 Kevin Weng
2019-07-10 11:17 ` Pierre Le Magourou
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=20190619202149.GA12516@localhost \
--to=bunk@stusta.de \
--cc=lemagoup@gmail.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 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.