From: Michal Marek <mmarek@suse.cz>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kbuild@vger.kernel.org,
Debian kernel maintainers <debian-kernel@lists.debian.org>,
Joerg Roedel <joerg.roedel@amd.com>,
Maximilian Attems <max@stro.at>
Subject: Re: [PATCH] builddeb: Don't create files in /tmp with predictable names
Date: Sat, 18 Feb 2012 22:34:57 +0100 [thread overview]
Message-ID: <20120218213457.GA8332@sepie.suse.cz> (raw)
In-Reply-To: <1329315449.3048.78.camel@deadeye>
On Wed, Feb 15, 2012 at 02:17:29PM +0000, Ben Hutchings wrote:
> The current use of /tmp for file lists is insecure. Put them under
> $objtree/debian instead.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Cc: stable@vger.kernel.org
Thanks, applied. How could I have missed that bug :-/.
Michal
prev parent reply other threads:[~2012-02-18 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 14:17 [PATCH] builddeb: Don't create files in /tmp with predictable names Ben Hutchings
2012-02-15 15:24 ` Maximilian Attems
2012-02-15 16:36 ` Joerg Roedel
2012-02-18 21:34 ` Michal Marek [this message]
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=20120218213457.GA8332@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox