From f93188cb87bebd6bf8b6cf0f18ba4e078feaf12b Mon Sep 17 00:00:00 2001 From: Marta Rybczynska Date: Tue, 18 Feb 2025 16:55:29 +0100 Subject: vulnerabilities/classes: remove references to cve-check text format The text format has been removed, so also remove references and examples using this format. Replace with examples with the JSON format. (From yocto-docs rev: 3757ace0581e6279aa7c065b21cee56edfe985dd) Signed-off-by: Marta Rybczynska Signed-off-by: Antonin Godard (cherry picked from commit a52cd7bcadccc53e982f90d6e170d00798322597) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman --- documentation/ref-manual/classes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst index 5bd1d50947..45973befbe 100644 --- a/documentation/ref-manual/classes.rst +++ b/documentation/ref-manual/classes.rst @@ -563,7 +563,7 @@ You can also look for vulnerabilities in specific packages by passing ``-c cve_check`` to BitBake. After building the software with Bitbake, CVE check output reports are available in ``tmp/deploy/cve`` -and image specific summaries in ``tmp/deploy/images/*.cve`` or ``tmp/deploy/images/*.json`` files. +and image specific summaries in ``tmp/deploy/images/*.json`` files. When building, the CVE checker will emit build time warnings for any detected issues which are in the state ``Unpatched``, meaning that CVE issue seems to affect the software component -- cgit v1.2.3-54-g00ecf