Do you mean CVE-2022-35414? Regards, Marta

Hello Gaurav, The CVE STATUS "Patched" means that there was an issue in the past, but it is either fixed or otherwise mitigated. Open issues are marked as "Unpatched". If you'd like to see only Unpatc

#yocto

Hello all, We're trying to use create-spdx.bbclass with meta-zephyr. However, this is failing with errors like the one at the bottom of the message. While digging deeper, it is hard to reproduce relia

When running master-next I have found one missing rename, cve-check has "CVE STATUS" result which is still Patched, Unpatched, Whitelisted. I propose to rename Whitelisted to Ignored to be in-line wit

(correcting the wrong list address) It looks like a possibility, I will give it a try. I have a question about the future, however. Currently meta-hardening is defining its own distribution. When hard

A number of typo fixes: - tmp->tpm in the DISTRO_FEATURES - update the mailing list address as it was out of date - update the distro name in the subject Signed-off-by: Marta Rybczynska <rybczynska@gm

A number of typo fixes: - tmp->tpm in the DISTRO_FEATURES - update the mailing list address as it was out of date - update the distro name in the subject Signed-off-by: Marta Rybczynska <rybczynska@gm

The address included in the meta-hardening documentation does not work and was changed in other places in 2019. Signed-off-by: Marta Rybczynska <rybczynska@...> --- meta-hardening/README | 6 +++

Compilers and related utils are better restricted on production platforms. Change permissions of all installed binutils tools to remove access from users outside of the root group. This also demonstra