From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcurl: Version bump. 7.83.0 -> 7.83.1
Date: Fri, 13 May 2022 14:49:24 +0200 [thread overview]
Message-ID: <Yn5T1M0HjLe85LS9@pengutronix.de> (raw)
In-Reply-To: <00d91654-31ce-1991-3292-88029a6edcca@t2data.com>
On Fri, May 13, 2022 at 10:42:51AM +0200, Christian Melki wrote:
> My bad.
>
> It needs to be removed. Included in the release.
> Daniel added it:
> https://github.com/curl/curl/commit/d7b970e46ba29a7e558e21d19f485977ffed6266
Ok, I'll fix it here.
Michael
> /Christian
>
> On 5/13/22 10:35 AM, Michael Olbrich wrote:
> > On Wed, May 11, 2022 at 09:20:28AM +0200, Christian Melki wrote:
> > > Usual churn of fixes.
> > > Curl is seeing an accelerated CVE ticketing.
> > > Probably due to a functioning bug bounty program.
> > > https://hackerone.com/curl?type=team
> > > With 30 reports in the last 90 days.
> > > So probably expect more CVEs in the near future.
> > >
> > > Changelog: https://curl.se/changes.html
> > > Security: https://curl.se/docs/security.html
> > >
> > > Plugs CVEs: CVE-2022-30115, CVE-2022-27782, CVE-2022-27781,
> > > CVE-2022-27780, CVE-2022-27779, CVE-2022-27778
> >
> > The old version has a patch. It's from upstream, but I'm not sure if it got
> > applied to the bugfix release.
> >
> > Michael
> >
> > > Signed-off-by: Christian Melki <christian.melki@t2data.com>
> > > ---
> > > rules/libcurl.make | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/rules/libcurl.make b/rules/libcurl.make
> > > index 3840b2abd..8faa948bf 100644
> > > --- a/rules/libcurl.make
> > > +++ b/rules/libcurl.make
> > > @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBCURL) += libcurl
> > > #
> > > # Paths and names
> > > #
> > > -LIBCURL_VERSION := 7.83.0
> > > -LIBCURL_MD5 := b7924acdea33dedc3150a044789ed0bb
> > > +LIBCURL_VERSION := 7.83.1
> > > +LIBCURL_MD5 := 08c6d9c25d9cf8d17be28363753e42ca
> > > LIBCURL := curl-$(LIBCURL_VERSION)
> > > LIBCURL_SUFFIX := tar.xz
> > > LIBCURL_URL := https://curl.haxx.se/download/$(LIBCURL).$(LIBCURL_SUFFIX)
> > > --
> > > 2.34.1
> > >
> > >
> > >
> >
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-05-13 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 7:20 Christian Melki
2022-05-11 10:49 ` Alexander Dahl
2022-05-13 8:35 ` Michael Olbrich
2022-05-13 8:42 ` Christian Melki
2022-05-13 12:49 ` Michael Olbrich [this message]
2022-05-25 9:45 ` [ptxdist] [APPLIED] " Michael Olbrich
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=Yn5T1M0HjLe85LS9@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