From: Eric Bavier <ericbavier@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Handling ‘file’ CVE
Date: Thu, 13 Nov 2014 12:47:00 -0600 [thread overview]
Message-ID: <87h9y3uee3.fsf@gmail.com> (raw)
In-Reply-To: <87egt7f052.fsf@yeeloong.lan>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
Mark H Weaver writes:
> Finally, 'file' is a propagated-input for 'intltool', which means that
> if anyone installs 'intltool' in their profile, they will have the buggy
> 'file' in their PATH.
The attached patch might be enough to fix this.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-intltool-Make-file-a-regular-input.patch --]
[-- Type: text/x-diff, Size: 1583 bytes --]
From fff25ec0451a65ccd5972d16ef96221c85084566 Mon Sep 17 00:00:00 2001
From: Eric Bavier <bavier@member.fsf.org>
Date: Thu, 13 Nov 2014 12:46:04 -0600
Subject: [PATCH] gnu: intltool: Make file a regular input.
* gnu/packages/glib.scm (intltool)[propagated-inputs]: Move file from here...
[inputs]: to here.
[arguments]: New 'patch-file-references phase.
---
gnu/packages/glib.scm | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm
index 9076643..212d3b6 100644
--- a/gnu/packages/glib.scm
+++ b/gnu/packages/glib.scm
@@ -250,16 +250,21 @@ bindings to call into the C library.")
(base32
"01j4yd7i84n9nk4ccs6yifg84pp68nr9by57jdbhj7dpdxf5rwk7"))))
(build-system gnu-build-system)
+ (inputs
+ `(("file" ,file)))
(propagated-inputs
`(;; Propagate gettext because users expect it to be there, and so does
;; the `intltool-update' script.
("gettext" ,gnu-gettext)
- ;; `file' is used by `intltool-update' too.
- ("file" ,file)
-
("perl-xml-parser" ,perl-xml-parser)
("perl" ,perl)))
+ (arguments
+ `(#:phases (alist-cons-after
+ 'unpack 'patch-file-references
+ (lambda _
+ (substitute* "intltool-update.in"
+ (("`file") (string-append "`" (which "file"))))))))
(home-page "https://launchpad.net/intltool/+download")
(synopsis "Tools to centralise translations of different file formats")
(description
--
1.7.9.5
[-- Attachment #3: Type: text/plain, Size: 133 bytes --]
--
Eric Bavier
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
next prev parent reply other threads:[~2014-11-13 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 10:41 Handling ‘file’ CVE Ludovic Courtès
2014-11-13 13:00 ` Andreas Enge
2014-11-13 13:17 ` Ludovic Courtès
2014-11-13 16:54 ` Ludovic Courtès
2014-11-13 18:03 ` Mark H Weaver
2014-11-13 18:47 ` Eric Bavier [this message]
2014-11-13 20:13 ` Ludovic Courtès
2014-11-13 20:42 ` Eric Bavier
2014-11-13 20:43 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9y3uee3.fsf@gmail.com \
--to=ericbavier@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).