all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: mupdf: Fix CVE-2016-8674.
Date: Wed, 26 Oct 2016 15:17:27 +0100	[thread overview]
Message-ID: <87oa27chzc.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87shrjs2hz.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

>> From c51f44edf3293aae323eded49dcba750f54607cb Mon Sep 17 00:00:00 2001
>> From: Marius Bakke <mbakke@fastmail.com>
>> Date: Wed, 26 Oct 2016 06:39:34 +0100
>> Subject: [PATCH] gnu: mupdf: Modify CVE-2016-8674 patch to apply to 1.9a.
>>
>> The fix from upstream did not apply cleanly due to many context changes.
>> This was adapted by cloning mupdf 1.9a from git and fixing conflicts
>> after applying our patches and cherry-picking upstream commit 1e03c06.
>>
>> * gnu/packages/patches/mupdf-CVE-2016-8674.patch: Adapt to 1.9a.
>
> I’m in favor of you pushing this patch.
>
> We can always adjust later if need be, but it’s better than keeping
> mupdf broken.

Okay. I applied this as 39df253e2bb260e67d8ce81431a9aa3478689774 with a
reference to the original commit. Testing encouraged!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

  reply	other threads:[~2016-10-26 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 16:53 [PATCH] gnu: mupdf: Fix CVE-2016-8674 Kei Kebreau
2016-10-25 17:12 ` Leo Famulari
2016-10-26  1:46   ` Mark H Weaver
2016-10-26  3:49     ` Kei Kebreau
2016-10-26  6:11       ` Marius Bakke
2016-10-26 12:45         ` Ludovic Courtès
2016-10-26 14:17           ` Marius Bakke [this message]
2016-10-26  9:25       ` Mark H Weaver

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=87oa27chzc.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --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 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.