[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Libtiff CVE-2016-5652
|
From: |
Leo Famulari |
|
Subject: |
Re: Libtiff CVE-2016-5652 |
|
Date: |
Sun, 30 Oct 2016 19:33:59 -0400 |
|
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Sun, Oct 30, 2016 at 10:56:41PM +0100, Ludovic Courtès wrote:
> Leo Famulari <address@hidden> skribis:
> > From 7abe86a8d93e1a1ed11f14ec7ede22ce9b020611 Mon Sep 17 00:00:00 2001
> > From: Leo Famulari <address@hidden>
> > 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...