From: Fernando Luiz Cola via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Fernando Luiz Cola <fernando.luiz@pantacor.com>
Subject: [ptxdist] [PATCH] mbedtls: version bump 2.28.0 -> 2.28.10
Date: Tue, 17 Nov 2026 11:40:28 -0300 [thread overview]
Message-ID: <20261117144028.34074-1-fernando.luiz@pantacor.com> (raw)
2.28.10 is the last release of the 2.28 LTS branch and carries its
security fixes.
Mbed TLS is now dual-licensed Apache-2.0 OR GPL-2.0-or-later. LICENSE
gained a header saying so and the GPL-2.0 text after the unchanged
Apache-2.0 text.
Pin the new MBEDTLS_CONFIG_FILE and MBEDTLS_USER_CONFIG_FILE cache
variables to empty, which keeps the default configuration.
Signed-off-by: Fernando Luiz Cola <fernando.luiz@pantacor.com>
---
Build-tested for DistroKit v8a (arm64) without further patches: builds and
installs, 'ptxdist licensecheck mbedtls' passes and configure_helper.py shows
no missing options. Not run on target.
rules/mbedtls.make | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/rules/mbedtls.make b/rules/mbedtls.make
index 42b60c559..bfa875109 100644
--- a/rules/mbedtls.make
+++ b/rules/mbedtls.make
@@ -15,15 +15,15 @@ PACKAGES-$(PTXCONF_MBEDTLS) += mbedtls
#
# Paths and names
#
-MBEDTLS_VERSION := 2.28.0
-MBEDTLS_SHA256 := 6519579b836ed78cc549375c7c18b111df5717e86ca0eeff4cb64b2674f424cc
+MBEDTLS_VERSION := 2.28.10
+MBEDTLS_SHA256 := 0f2e0525903a89ae1d39ce439d858be66933bda54c5b6102b72a29ed8fe7c088
MBEDTLS := mbedtls-$(MBEDTLS_VERSION)
MBEDTLS_SUFFIX := tar.gz
MBEDTLS_URL := https://github.com/Mbed-TLS/mbedtls/archive/refs/tags/v$(MBEDTLS_VERSION).$(MBEDTLS_SUFFIX)
MBEDTLS_SOURCE := $(SRCDIR)/$(MBEDTLS).$(MBEDTLS_SUFFIX)
MBEDTLS_DIR := $(BUILDDIR)/$(MBEDTLS)
-MBEDTLS_LICENSE := Apache-2.0
-MBEDTLS_LICENSE_FILES := file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57
+MBEDTLS_LICENSE := Apache-2.0 OR GPL-2.0-or-later
+MBEDTLS_LICENSE_FILES := file://LICENSE;md5=379d5819937a6c2f1ef1630d341e026d
# ----------------------------------------------------------------------------
# Prepare
@@ -41,7 +41,9 @@ MBEDTLS_CONF_OPT := \
-DINSTALL_MBEDTLS_HEADERS=ON \
-DLINK_WITH_PTHREAD=ON \
-DLINK_WITH_TRUSTED_STORAGE=OFF \
+ -DMBEDTLS_CONFIG_FILE= \
-DMBEDTLS_FATAL_WARNINGS=OFF \
+ -DMBEDTLS_USER_CONFIG_FILE= \
-DUNSAFE_BUILD=OFF \
-DUSE_PKCS11_HELPER_LIBRARY=OFF \
-DUSE_SHARED_MBEDTLS_LIBRARY=ON \
--
2.43.0
reply other threads:[~2026-11-17 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261117144028.34074-1-fernando.luiz@pantacor.com \
--to=ptxdist@pengutronix.de \
--cc=fernando.luiz@pantacor.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