all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 0/1] Help wanted grafting Expat (CVE-2016-0718)
Date: Wed, 18 May 2016 12:36:50 -0400	[thread overview]
Message-ID: <cover.1463589188.git.leo@famulari.name> (raw)

I've attached my attempt at fixing CVE-2016-0718 in Expat [0]. The
grafted expat updates to 2.1.1 and applies the patch from [1].

The problem is that, when trying build something that depends on expat,
I seem to have to rebuild *many* things.

Any advice?

By the way, there are some other caveats with this change.

First, I don't yet know the relationship of the patch from oss-sec to
upstream. It's not in their git repo. It might be a squashed
representation of the branch 'cve-2016-0718-fix-2-2-1' that they merged
yesterday [2]. I changed the line endings from DOS to Unix.

Second, I updated the grafted expat to 2.1.1 since the patch did not
apply to 2.1.0. I don't know if 2.1.1 is binary compatible with 2.1.0,
so I don't know if it's even suitable for grafting.

[0]
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

[1]
http://seclists.org/oss-sec/2016/q2/360

[2]
https://sourceforge.net/p/expat/code_git/ci/be4b1c06daba1849b8ff5e00bae5caf47f6c39fd/

Leo Famulari (1):
  gnu: expat: Fix CVE-2016-0718.

 gnu/local.mk                                   |   1 +
 gnu/packages/patches/expat-CVE-2016-0718.patch | 755 +++++++++++++++++++++++++
 gnu/packages/xml.scm                           |  25 +-
 3 files changed, 779 insertions(+), 2 deletions(-)
 create mode 100644 gnu/packages/patches/expat-CVE-2016-0718.patch

-- 
2.8.2

             reply	other threads:[~2016-05-18 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 16:36 Leo Famulari [this message]
2016-05-18 16:36 ` [PATCH 1/1] gnu: expat: Fix CVE-2016-0718 Leo Famulari
2016-05-18 17:37 ` [PATCH 0/1] Help wanted grafting Expat (CVE-2016-0718) Leo Famulari
2016-05-19 12:19   ` Ludovic Courtès
2016-05-19 14:36     ` 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=cover.1463589188.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=guix-devel@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.