Re-adding yocto@.
> This brings me to the handling of the "Unpatched" CVEs in the project. I can
> get some idea for which version of the package may have the mitigation for
> the CVE but there is no "mitigated_version" variable which helps me figure
> out the updated path in an automated way.
On Tue, Jul 5, 2022 at 2:31 PM wrote:
>
> I used the cve check class by including it in the local.conf and then ran the
> bitbake build process for my image. I got a log of all the detected CVEs in
> the packages used in the build. However, on closer inspection, I noticed that
> the packages us
> On 5 Jul 2022, at 13:31, gauravsuman007 via lists.yoctoproject.org
> wrote:
>
> I used the cve check class by including it in the local.conf and then ran the
> bitbake build process for my image. I got a log of all the detected CVEs in
> the packages used in the build. However, on closer in
I used the cve check class by including it in the local.conf and then ran the
bitbake build process for my image. I got a log of all the detected CVEs in the
packages used in the build. However, on closer inspection, I noticed that the
packages used in the build are already higher version than w
