From: Leo Famulari <leo@famulari.name>
To: 47563@debbugs.gnu.org
Subject: bug#47563: [PATCH 0/1] gnu: curl: Fix CVE-2021-22876 and CVE-2021-22890.
Date: Fri, 2 Apr 2021 14:22:06 -0400 [thread overview]
Message-ID: <YGdgzne+guUD0JCT@jasmine.lan> (raw)
In-Reply-To: <20210402140940.28300-1-lle-bout@zaclys.net>
On Fri, Apr 02, 2021 at 04:09:39PM +0200, Léo Le Bouter via Bug reports for GNU Guix wrote:
> curl-CVE-2021-22876.patch was rebased onto 7.74.0, but curl-CVE-2021-22890.patch
> does not apply and please I need help rebasing it, it looks quite complex.
>
> I pushed an upgrade of curl to 7.76.0 which has been much much easier to
> core-updates already as
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=2e0b1b62e94b926041ca9af70537dd9b3ab64edf
> but unfortunately since curl requires so many rebuilds it seems we can't use
> such commit on master for now.
Can we try grafting an "upgrade" to 7.76.0? In my experience, most curl
upgrades are graftable.
Curl's developers are very careful with their ABI and even maintain
their own page on the subject: <https://curl.se/libcurl/abi.html>
next prev parent reply other threads:[~2021-04-02 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 14:04 bug#47563: curl is vulnerable to CVE-2021-22890 and CVE-2021-22876 Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 14:09 ` bug#47563: [PATCH 0/1] gnu: curl: Fix CVE-2021-22876 and CVE-2021-22890 Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 14:09 ` bug#47563: [PATCH 1/1] " Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 18:22 ` Leo Famulari [this message]
2021-04-02 18:43 ` bug#47563: [PATCH 0/1] " Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 19:24 ` bug#47563: [PATCH] gnu: curl: Update to 7.76.0 [security fixes] Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 19:33 ` bug#47563: [PATCH v2] " Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 19:34 ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 20:36 ` Leo Famulari
2021-04-02 20:46 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YGdgzne+guUD0JCT@jasmine.lan \
--to=leo@famulari.name \
--cc=47563@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).