From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 01/01: gnu: curl: Update replacement to 7.52.0 [fixes CVE-2016-{9586, 9952, 9953}].
Date: Wed, 21 Dec 2016 11:58:44 -0500 [thread overview]
Message-ID: <20161221165844.GA7240@jasmine> (raw)
In-Reply-To: <20161221140321.922BB220166@vcs.savannah.gnu.org>
On Wed, Dec 21, 2016 at 02:03:21PM +0000, Marius Bakke wrote:
> mbakke pushed a commit to branch master
> in repository guix.
>
> commit 42366b35c3f9f8dc8b059d3369b8196a4b832c18
> Author: Marius Bakke <mbakke@fastmail.com>
> Date: Wed Dec 21 14:56:34 2016 +0100
>
> gnu: curl: Update replacement to 7.52.0 [fixes CVE-2016-{9586,9952,9953}].
>
> * gnu/packages/curl.scm (curl)[replacement]: Update to 7.52.0.
> (curl-7.51.0): Replace with ...
> (curl-7.52.0): ... this.
ng0 pointed out this message from the curl maintainers:
"Attention! We will release a patch update within a few days to fix a
serious security problem found in curl 7.52.0. You may consider holding
off until then."
https://curl.haxx.se/download.html
So, I reverted the update for now. It seems like this new bug is more
serious than the security bug fixed in 7.52.0, CVE-2016-9586: printf
floating point buffer overflow. The other two named bugs fixed in 7.52.0
only manifest on Windows CE with the schannel TLS implementation, if I
understand correctly.
next parent reply other threads:[~2016-12-21 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161221140321.28790.1100@vcs.savannah.gnu.org>
[not found] ` <20161221140321.922BB220166@vcs.savannah.gnu.org>
2016-12-21 16:58 ` Leo Famulari [this message]
2016-12-21 19:27 ` 01/01: gnu: curl: Update replacement to 7.52.0 [fixes CVE-2016-{9586, 9952, 9953}] Marius Bakke
2016-12-23 9:12 ` ng0
2016-12-23 14:31 ` Marius Bakke
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=20161221165844.GA7240@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.