From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCH] gnu: mupdf: Fix CVE-2016-8674. Date: Wed, 26 Oct 2016 05:25:06 -0400 Message-ID: <87h97za2dp.fsf@netris.org> References: <87twc0s73r.fsf@openmailbox.org> <20161025171235.GA4569@jasmine> <87lgxbanmm.fsf@netris.org> <874m3z7osh.fsf@openmailbox.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55699) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzKSb-0004RE-K5 for guix-devel@gnu.org; Wed, 26 Oct 2016 05:25:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzKSX-00084j-0X for guix-devel@gnu.org; Wed, 26 Oct 2016 05:25:25 -0400 Received: from world.peace.net ([50.252.239.5]:42077) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bzKSW-00084S-TF for guix-devel@gnu.org; Wed, 26 Oct 2016 05:25:20 -0400 In-Reply-To: <874m3z7osh.fsf@openmailbox.org> (Kei Kebreau's message of "Tue, 25 Oct 2016 23:49:18 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Kei Kebreau Cc: guix-devel@gnu.org Kei Kebreau writes: > Mark H Weaver writes: > >> Leo Famulari writes: >> >>> On Tue, Oct 25, 2016 at 12:53:28PM -0400, Kei Kebreau wrote: >>>> Fix for >>>> https://blogs.gentoo.org/ago/2016/09/22/mupdf-use-after-free-in-pdf_to_num-pdf-object-c/. >>> >>>> From 97312c3c9e13688081aa513d1c94a9fff1274f75 Mon Sep 17 00:00:00 2001 >>>> From: Kei Kebreau >>>> Date: Tue, 25 Oct 2016 12:49:52 -0400 >>>> Subject: [PATCH] gnu: mupdf: Fix CVE-2016-8674. >>>> >>>> * gnu/packages/patches/mupdf-CVE-2016-8674.patch: New file. >>>> * gnu/local.mk (dist_patch_DATA): Add it. >>>> * gnu/packages/pdf.scm (mupdf): Use it. >>> >>> Thank you, please push! >> >> mupdf-CVE-2016-8674.patch fails to apply: >> >> https://hydra.gnu.org/build/1581228/nixlog/2/tail-reload >> >> Kei, did you test this? >> >> Mark > I did not. It was a bad slip up, as I tested all of the rest of my > patches today. I'll be significantly more careful with future security > commits. > > Is it frowned upon to revert that commit on its own (it's the third to > last commit as I write this), or should I attempt to patch on top of it? Either way is fine with me. Thanks! Mark