From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Libtiff CVE-2016-5652
Date: Sun, 30 Oct 2016 19:33:59 -0400 [thread overview]
Message-ID: <20161030233359.GA20183@jasmine> (raw)
In-Reply-To: <87h97tsdpi.fsf@gnu.org>
On Sun, Oct 30, 2016 at 10:56:41PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> > From 7abe86a8d93e1a1ed11f14ec7ede22ce9b020611 Mon Sep 17 00:00:00 2001
> > From: Leo Famulari <leo@famulari.name>
> > Date: Sat, 29 Oct 2016 19:23:05 -0400
> > Subject: [PATCH] gnu: libtiff: Fix CVE-2016-5652.
> >
> > * gnu/packages/patches/libtiff-CVE-2016-5652.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/image.scm (libtiff/fixed)[source]: Use it.
>
> I’d say go for it.
Pushed to master and merged into core-updates. I kept it grafted on
core-updates, since changing libtiff requires ~1500 rebuilds. Oh well.
It's a good candidate for a post-release "staging" branch.
> 0 days since the last image library vulnerability…
I don't think we'll need 64 bits for this counter...
prev parent reply other threads:[~2016-10-30 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 23:41 Libtiff CVE-2016-5652 Leo Famulari
2016-10-30 21:56 ` Ludovic Courtès
2016-10-30 23:33 ` Leo Famulari [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
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=20161030233359.GA20183@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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).