From: yurade <yogita.urade@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [oe][meta-oe][kirkstone][PATCH 2/2] mbedtls: upgrade 2.28.7->2.28.8
Date: Fri, 26 Apr 2024 13:04:43 +0000 [thread overview]
Message-ID: <20240426130443.2098001-2-yogita.urade@windriver.com> (raw)
In-Reply-To: <20240426130443.2098001-1-yogita.urade@windriver.com>
From: Yogita Urade <yogita.urade@windriver.com>
Includes security fixes for:
CVE-2024-28960 - Insecure handling of shared memory in PSA Crypto APIs
Release notes:
https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.8
Signed-off-by: Yogita Urade <yogita.urade@windriver.com>
---
.../mbedtls/{mbedtls_2.28.7.bb => mbedtls_2.28.8.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-networking/recipes-connectivity/mbedtls/{mbedtls_2.28.7.bb => mbedtls_2.28.8.bb} (94%)
diff --git a/meta-networking/recipes-connectivity/mbedtls/mbedtls_2.28.7.bb b/meta-networking/recipes-connectivity/mbedtls/mbedtls_2.28.8.bb
similarity index 94%
rename from meta-networking/recipes-connectivity/mbedtls/mbedtls_2.28.7.bb
rename to meta-networking/recipes-connectivity/mbedtls/mbedtls_2.28.8.bb
index 758a2118f1..45e196b995 100644
--- a/meta-networking/recipes-connectivity/mbedtls/mbedtls_2.28.7.bb
+++ b/meta-networking/recipes-connectivity/mbedtls/mbedtls_2.28.8.bb
@@ -23,8 +23,8 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=379d5819937a6c2f1ef1630d341e026d"
SECTION = "libs"
S = "${WORKDIR}/git"
-SRCREV = "555f84735aecdbd76a566cf087ec8425dfb0c8ab"
-SRC_URI = "git://github.com/ARMmbed/mbedtls.git;protocol=https;branch=mbedtls-2.28"
+SRCREV = "5a764e5555c64337ed17444410269ff21cb617b1"
+SRC_URI = "git://github.com/Mbed-TLS/mbedtls.git;protocol=https;branch=mbedtls-2.28"
inherit cmake update-alternatives
--
2.40.0
prev parent reply other threads:[~2024-04-26 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 13:04 [oe][meta-oe][kirkstone][PATCH 1/2] mbedtls: upgrade 3.5.2->3.6.0 yurade
2024-04-26 13:04 ` yurade [this message]
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=20240426130443.2098001-2-yogita.urade@windriver.com \
--to=yogita.urade@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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).