From: "Léo Le Bouter via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: leo@famulari.name, 47563@debbugs.gnu.org
Subject: bug#47563: [PATCH 0/1] gnu: curl: Fix CVE-2021-22876 and CVE-2021-22890.
Date: Fri, 02 Apr 2021 20:43:59 +0200 [thread overview]
Message-ID: <6d54754e99e6dabb669e16b2036485fbaa64b318.camel@zaclys.net> (raw)
In-Reply-To: <YGdgzne+guUD0JCT@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
On Fri, 2021-04-02 at 14:22 -0400, Leo Famulari wrote:
>
> 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>
If you think that's OK, let's do it!
I see indeed from that page there should be no problem.
Will send a patch shortly.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-02 18:45 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 ` bug#47563: [PATCH 0/1] " Leo Famulari
2021-04-02 18:43 ` Léo Le Bouter via Bug reports for GNU Guix [this message]
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=6d54754e99e6dabb669e16b2036485fbaa64b318.camel@zaclys.net \
--to=bug-guix@gnu.org \
--cc=47563@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=lle-bout@zaclys.net \
/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).