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: 9798689e4f4b74163c2e8594f3d1ce082d295aa1)

Signed-off-by: Marta Rybczynska <marta.rybczynska@ygreky.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit a52cd7bcadccc53e982f90d6e170d00798322597)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
Marta Rybczynska
2025-02-18 16:55:29 +01:00
committed by Steve Sakoman
parent 3a36dce7e5
commit 47cb7bfa66
2 changed files with 69 additions and 29 deletions

View File

@@ -488,7 +488,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