From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libcurl: Version bump. 8.17.0 -> 8.18.0
Date: Fri, 23 Jan 2026 16:01:59 +0100 [thread overview]
Message-ID: <20260123150159.1557411-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260111153303.2713046-1-christian.melki@t2data.com>
Thanks, applied as 9bac0d372c8001dbfe78da9c78851fde26fcf7ec.
Michael
[sent from post-receive hook]
On Fri, 23 Jan 2026 16:01:59 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Bunch of fixes + security + minversion OpenSSL >= 3.0.0.
> https://curl.se/changes.html#8_18_0
>
> Plugs CVEs:
> CVE-2025-15224: libssh key passphrase bypass without agent set
> CVE-2025-15079: libssh global known_hosts override
> CVE-2025-14819: OpenSSL partial chain store policy bypass
> CVE-2025-14524: bearer token leak on cross-protocol redirect
> CVE-2025-14017: broken TLS options for threaded LDAPS
> CVE-2025-13034: No QUIC certificate pinning with GnuTLS
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260111153303.2713046-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libcurl.make b/rules/libcurl.make
> index e16c30cddcff..62d9a8ccbc8d 100644
> --- a/rules/libcurl.make
> +++ b/rules/libcurl.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBCURL) += libcurl
> #
> # Paths and names
> #
> -LIBCURL_VERSION := 8.17.0
> -LIBCURL_MD5 := 7a9d4b772fc56d68479b0416f234105a
> +LIBCURL_VERSION := 8.18.0
> +LIBCURL_MD5 := dae6088bf7af69d3b0a87c762de92248
> LIBCURL := curl-$(LIBCURL_VERSION)
> LIBCURL_SUFFIX := tar.xz
> LIBCURL_URL := https://curl.se/download/$(LIBCURL).$(LIBCURL_SUFFIX)
prev parent reply other threads:[~2026-01-23 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 15:33 [ptxdist] [PATCH] " Christian Melki
2026-01-23 15:01 ` Michael Olbrich [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=20260123150159.1557411-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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