all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: libtiff: Fix CVE-2016-{10092, 10093, 10094} and others.
Date: Tue, 10 Jan 2017 22:43:34 +0100	[thread overview]
Message-ID: <8737gqzj3t.fsf@gnu.org> (raw)
In-Reply-To: <3d2d557f00e78cde98d4b538e1315b809124df53.1484072055.git.leo@famulari.name> (Leo Famulari's message of "Tue, 10 Jan 2017 13:14:16 -0500")

Leo Famulari <leo@famulari.name> skribis:

> * gnu/packages/patches/libtiff-CVE-2016-10092.patch,
> gnu/packages/patches/libtiff-CVE-2016-10093.patch,
> gnu/packages/patches/libtiff-CVE-2016-10094.patch,
> gnu/packages/patches/libtiff-assertion-failure.patch,
> gnu/packages/patches/libtiff-divide-by-zero-ojpeg.patch,
> gnu/packages/patches/libtiff-divide-by-zero-tiffcp.patch,
> gnu/packages/patches/libtiff-divide-by-zero-tiffcrop.patch,
> gnu/packages/patches/libtiff-divide-by-zero.patch,
> gnu/packages/patches/libtiff-heap-overflow-pixarlog-luv.patch,
> gnu/packages/patches/libtiff-heap-overflow-tif-dirread.patch,
> gnu/packages/patches/libtiff-heap-overflow-tiffcp.patch,
> gnu/packages/patches/libtiff-heap-overflow-tiffcrop.patch,
> gnu/packages/patches/libtiff-invalid-read.patch,
> gnu/packages/patches/libtiff-null-dereference.patch,
> gnu/packages/patches/libtiff-tiffcp-underflow.patch: New files.
> * gnu/local.mk (dist_patch_DATA): Add them.
> * gnu/packages/image.scm (libtiff)[replacement]: New field.
> (libtiff/fixed): New variable.

Impressive list (most from oss-sec on Jan. 1st, right?).

I skimmed over the patches; some are obvious, others much less, but I
didn’t notice anything suspicious.  I’d say go for it.

Thanks *a lot* for taking the time to prepare this patch!

Ludo’.

  reply	other threads:[~2017-01-10 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 18:14 [PATCH 1/1] gnu: libtiff: Fix CVE-2016-{10092, 10093, 10094} and others Leo Famulari
2017-01-10 21:43 ` Ludovic Courtès [this message]
2017-01-10 22:33   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737gqzj3t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.