Re: Files-Excluded field and security implications of uscan and debian/copyright.

To: debian-devel@lists.debian.org
Subject: Re: Files-Excluded field and security implications of uscan and debian/copyright.
From: Charles Plessy <plessy@debian.org>
Date: Fri, 7 Sep 2012 13:11:46 +0900
Message-id: <[🔎] 20120907041146.GC21903@falafel.plessy.net>
In-reply-to: <[🔎] 20120906234436.GA7066@falafel.plessy.net>
References: <20120821102121.GD14977@an3as.eu> <CAKTje6HhD392gEPadjMXkQE3VFG5J++qG1fKdRQn4sjF9bz3cw@mail.gmail.com> <20120822080938.GG8759@jones.dk> <20120825040303.GE2450@falafel.plessy.net> <[🔎] 20120906234436.GA7066@falafel.plessy.net>

Le Fri, Sep 07, 2012 at 08:44:36AM +0900, Charles Plessy a écrit :
> 
> in the case of the Files-Excluded field, the contents of the field are directly
> executed.

I mean: the contents are transferred to an expression that is directly executed.

Sorry for the noise,

-- 
Charles

Reply to:

Follow-Ups:
- Re: Files-Excluded field and security implications of uscan and debian/copyright.
  - From: Ian Jackson <ijackson@chiark.greenend.org.uk>

References:
- Files-Excluded field and security implications of uscan and debian/copyright.
  - From: Charles Plessy <plessy@debian.org>

Prev by Date: Bug#686903: RFP: pass -- the standard unix password manager
Next by Date: Re: bits from the DPL: August 2012
Previous by thread: Files-Excluded field and security implications of uscan and debian/copyright.
Next by thread: Re: Files-Excluded field and security implications of uscan and debian/copyright.
Index(es):
- Date
- Thread