From: Leo Famulari <leo@famulari.name>
To: Kei Kebreau <kei@openmailbox.org>
Cc: 26804@debbugs.gnu.org
Subject: bug#26804: [PATCH] gnu: libtiff: Fix CVE-2017-{7593, 7594, 7595, 7596, 7597, 7598, 7599, 7600, 7601, 7602}.
Date: Sat, 6 May 2017 14:54:50 -0400 [thread overview]
Message-ID: <20170506185450.GB22485@jasmine> (raw)
In-Reply-To: <20170506144557.28785-1-kei@openmailbox.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Sat, May 06, 2017 at 10:45:57AM -0400, Kei Kebreau wrote:
> * gnu/packages/patches/libtiff-CVE-2017-7593.patch: New file.
> * gnu/packages/patches/libtiff-CVE-2017-7594.patch: New file.
> * gnu/packages/patches/libtiff-multiple-UBSAN-crashes.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add them.
> * gnu/packages/image.scm (libtiff)[source]: Use them.
Thank you!
This change should be grafted, since ~2000 packages will be affected.
There's a recent example of appending patches in a replacement package:
+ (source
+ (origin
+ (inherit (package-source libsndfile))
+ (patches
+ (append
+ (origin-patches (package-source libsndfile))
+ (search-patches "libsndfile-CVE-2017-8361-8363-8365.patch"
+ "libsndfile-CVE-2017-8362.patch")))))))
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=1c4a500aae53b8cd33d1266eb3809b859ae2555d
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-06 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 14:45 bug#26804: [PATCH] gnu: libtiff: Fix CVE-2017-{7593, 7594, 7595, 7596, 7597, 7598, 7599, 7600, 7601, 7602} Kei Kebreau
2017-05-06 18:54 ` Leo Famulari [this message]
2017-05-07 0:11 ` Kei Kebreau
2017-05-07 3:41 ` Leo Famulari
2017-05-07 10:58 ` Kei Kebreau
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=20170506185450.GB22485@jasmine \
--to=leo@famulari.name \
--cc=26804@debbugs.gnu.org \
--cc=kei@openmailbox.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.