Skip to contentSkip to conversation

set CVE_PRODUCT

PATCH New Mikko Rapeli 1 participant 2 messages Jul 21, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 set CVE_PRODUCT

This way yocto cve-check can find open CVE's for qt5 recipes. See also:

http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139897.html

"Results from cve-check are not very good at the moment.
One of the reasons for this is that component names used in CVE database differ from yocto recipe names. This series fixes several of those name mapping problems by setting the CVE_PRODUCT correctly in the recipes. To check this mapping with after a build, I'm exporting LICENSE and CVE_PRODUCT variables to buildhistory for recipes and packages."

Mikko Rapeli (1):
qt5-git.inc: set CVE_PRODUCT to qt

 recipes-qt/qt5/qt5-git.inc | 2 ++
 1 file changed, 2 insertions(+)
Signature · 1 line
1.9.1
#1 lore raw

PATCH 1/1 qt5-git.inc: set CVE_PRODUCT to qt

It is used in NVD for CVE's like:

https://nvd.nist.gov/vuln/detail/CVE-2015-1860

---
 recipes-qt/qt5/qt5-git.inc | 2 ++
 1 file changed, 2 insertions(+)
recipes-qt/qt5/qt5-git.inc +2 -0
index f864953..1cb115f 100644
@@ -10,6 +10,8 @@ SRC_URI = " \
     ${QT_GIT}/${QT_MODULE}.git;name=${QT_MODULE};${QT_MODULE_BRANCH_PARAM};protocol=${QT_GIT_PROTOCOL} \
 "
 
+CVE_PRODUCT = "qt"
+
 S = "${WORKDIR}/git"
 
 PV = "5.8.0+git${SRCPV}"
Signature · 1 line
1.9.1