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.0.1 -> 8.1.1
Date: Fri, 2 Jun 2023 09:17:45 +0200 [thread overview]
Message-ID: <20230602071745.1512273-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230526042927.1858867-1-christian.melki@t2data.com>
Thanks, applied as 0864a6b4e634f71531c21001bd9e61fa83a854c3.
Michael
[sent from post-receive hook]
On Fri, 02 Jun 2023 09:17:45 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> A slew of changes, mostly bugfixes.
> https://curl.se/changes.html#8_1_0
> https://curl.se/changes.html#8_1_1
>
> Including plugging four CVE:s.
> https://curl.se/docs/vuln-8.0.1.html
> CVE-2023-28319 - UAF in SSH sha256 fingerprint check
> CVE-2023-28320 - siglongjmp race condition
> CVE-2023-28321 - IDN wildcard match
> CVE-2023-28322 - more POST-after-PUT confusion
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230526042927.1858867-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 76dc732b5770..0216a9e231c3 100644
> --- a/rules/libcurl.make
> +++ b/rules/libcurl.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBCURL) += libcurl
> #
> # Paths and names
> #
> -LIBCURL_VERSION := 8.0.1
> -LIBCURL_MD5 := f6c2fdeb30ad30234378a56c28350845
> +LIBCURL_VERSION := 8.1.1
> +LIBCURL_MD5 := 624f8f7eb4b4699c5e69f081c17c7049
> LIBCURL := curl-$(LIBCURL_VERSION)
> LIBCURL_SUFFIX := tar.xz
> LIBCURL_URL := https://curl.se/download/$(LIBCURL).$(LIBCURL_SUFFIX)
prev parent reply other threads:[~2023-06-02 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 4:29 [ptxdist] [PATCH] " Christian Melki
2023-05-26 6:57 ` Michael Olbrich
2023-06-02 7:17 ` 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=20230602071745.1512273-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