mirror of
https://git.yoctoproject.org/poky
synced 2026-05-30 00:20:08 +00:00
manuals: further documentation for cve-check
This adds details about the actual implementation of vulnerability checks, about how to fix or ignore vulnerabilities in recipes, and documents the CVE_CHECK_PN_WHITELIST and CVE_CHECK_WHITELIST variables. (From yocto-docs rev: 55886d211218b3a604c2f8a29c854685ebf284dd) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reviewed-by: Quentin Schulz <foss@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
23e640b809
commit
4c7e3b64bc
@@ -404,6 +404,22 @@ cross-compilation tools used for building SDKs. See the
|
||||
section in the Yocto Project Overview and Concepts Manual for more
|
||||
discussion on these cross-compilation tools.
|
||||
|
||||
.. _ref-classes-cve-check:
|
||||
|
||||
``cve-check.bbclass``
|
||||
=====================
|
||||
|
||||
The ``cve-check`` class looks for known CVEs (Common Vulnerabilities
|
||||
and Exposures) while building an image. This class is meant to be
|
||||
inherited globally from a configuration file::
|
||||
|
||||
INHERIT += "cve-check"
|
||||
|
||||
You can also look for vulnerabilities in specific packages by passing
|
||||
``-c cve_check`` to BitBake. You will find details in the
|
||||
":ref:`dev-manual/common-tasks:checking for vulnerabilities`"
|
||||
section in the Development Tasks Manual.
|
||||
|
||||
.. _ref-classes-debian:
|
||||
|
||||
``debian.bbclass``
|
||||
|
||||
Reference in New Issue
Block a user