netcat: Set CPE_PRODUCT
PATCH 1/1 netcat: Set CPE_PRODUCT
This way yocto cve-check can find open CVE's. 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."
Value added is based on:
https://nvd.nist.gov/products/cpe/search/results?keyword=netcat&status=FINAL&orderBy=CPEURI&namingFormat=2.3
--- meta-networking/recipes-support/netcat/netcat_0.7.1.bb | 2 ++ 1 file changed, 2 insertions(+)
meta-networking/recipes-support/netcat/netcat_0.7.1.bb +2 -0
@@ -16,6 +16,8 @@ SRC_URI[sha256sum] = "b55af0bbdf5acc02d1eb6ab18da2acd77a400bafd074489003f3df0967 inherit autotools +CVE_PRODUCT = "netcat_project:netcat" + do_install_append() { install -d ${D}${bindir} mv ${D}${bindir}/nc ${D}${bindir}/nc.${BPN}
Signature · 1 line
2.24.1
On Thu, Jul 2, 2020 at 6:36 PM Andre Carvalho via lists.openembedded.org <[email protected]> wrote:
There is a typo in commit title
Andreas
Quoted 38 lines
This way yocto cve-check can find open CVE's. 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 theCVE_PRODUCTcorrectly in the recipes. To check this mapping with after a build, I'm exporting LICENSE andCVE_PRODUCTvariables to buildhistory for recipes and packages."Value added is based on:
https://nvd.nist.gov/products/cpe/search/results?keyword=netcat&status=FINAL&orderBy=CPEURI&namingFormat=2.3Signed-off-by Andre Carvalho <[email protected]>--- meta-networking/recipes-support/netcat/netcat_0.7.1.bb | 2 ++ 1 file changed, 2 insertions(+)meta-networking/recipes-support/netcat/netcat_0.7.1.bb +2
-1@@ -16,6 +16,8 @@ SRC_URI[sha256sum] = "b55af0bbdf5acc02d1eb6ab18da2acd77a400bafd074489003f3df0967 inherit autotools +CVE_PRODUCT = "netcat_project:netcat" + do_install_append() { install -d ${D}${bindir} mv ${D}${bindir}/nc ${D}${bindir}/nc.${BPN} --2.24.1
Quoted 3 lines · Andreas Müller
On Thu, Jul 2, 2020 at 6:36 PM Andre Carvalho via lists.openembedded.org <[email protected]> wrote:
There is a typo in commit title
yeah some users have seen this issue especially on patchwork this causes trouble too, I have to manually edit it when I apply the patch but such is life. I wished the mail systems were sane.
Quoted 42 lines
Andreas
Quoted 40 lines
This way yocto cve-check can find open CVE's. 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 theCVE_PRODUCTcorrectly in the recipes. To check this mapping with after a build, I'm exporting LICENSE andCVE_PRODUCTvariables to buildhistory for recipes and packages."Value added is based on:
https://nvd.nist.gov/products/cpe/search/results?keyword=netcat&status=FINAL&orderBy=CPEURI&namingFormat=2.3Signed-off-by Andre Carvalho <[email protected]>--- meta-networking/recipes-support/netcat/netcat_0.7.1.bb | 2 ++ 1 file changed, 2 insertions(+)meta-networking/recipes-support/netcat/netcat_0.7.1.bb +2
-1@@ -16,6 +16,8 @@ SRC_URI[sha256sum] = "b55af0bbdf5acc02d1eb6ab18da2acd77a400bafd074489003f3df0967 inherit autotools +CVE_PRODUCT = "netcat_project:netcat" + do_install_append() { install -d ${D}${bindir} mv ${D}${bindir}/nc ${D}${bindir}/nc.${BPN} --2.24.1