From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: meta-arm@lists.yoctoproject.org
Cc: Marta Rybczynska <rybczynska@gmail.com>,
Mikko Rapeli <mikko.rapeli@linaro.org>
Subject: [PATCH 0/4] RFC: detect CVEs from embedded mbedtls
Date: Thu, 19 Oct 2023 13:55:48 +0300 [thread overview]
Message-ID: <20231019105552.3631582-1-mikko.rapeli@linaro.org> (raw)
mbedtls is used inside tf-a and tf-m recipes and it's embedded using
SRC_URI to the build workspace. While it would better to use mbedtls
recipe from meta-openembedded, if at possible at all, at least try to
detect CVEs from current setup by setting CVE_PRODUCT and CVE_VERSION
for the embedded mbedtls.
RFC since depends on poky cve-check.bbclass patch
"cve-check.bbclass: support embedded SW components with different version number"
https://lists.openembedded.org/g/openembedded-core/message/189260
Mikko Rapeli (4):
trusted-firmware-a: include BSD-2-Clause license
trusted-firmware-a: set version of mbed_tls for CVE check
trusted-firmware-m: set CVE product and version for mbedtls
trusted-firmware-a: set CVE_VERSION for mbedtls too
.../trusted-firmware-a/trusted-firmware-a_2.8.6.bb | 2 +-
.../recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc | 4 +++-
.../trusted-firmware-a/trusted-firmware-a_2.9.0.bb | 2 +-
.../trusted-firmware-m/trusted-firmware-m-1.8.1-src.inc | 2 +-
.../recipes-bsp/trusted-firmware-m/trusted-firmware-m.inc | 2 ++
5 files changed, 8 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-19 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 10:55 Mikko Rapeli [this message]
2023-10-19 10:55 ` [PATCH 1/4] trusted-firmware-a: include BSD-2-Clause license Mikko Rapeli
2023-10-19 10:55 ` [PATCH 2/4] trusted-firmware-a: set version of mbed_tls for CVE check Mikko Rapeli
2023-10-19 10:55 ` [PATCH 3/4] trusted-firmware-m: set CVE product and version for mbedtls Mikko Rapeli
2023-10-19 10:55 ` [PATCH 4/4] trusted-firmware-a: set CVE_VERSION for mbedtls too Mikko Rapeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231019105552.3631582-1-mikko.rapeli@linaro.org \
--to=mikko.rapeli@linaro.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=rybczynska@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).