From: "Joshua Hudson" <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: World writable tarballs
Date: Sat, 29 Apr 2006 21:59:22 -0700 [thread overview]
Message-ID: <bda6d13a0604292159r3187b76fg56b137816480bf2a@mail.gmail.com> (raw)
In-Reply-To: <200604300148.12462.s0348365@sms.ed.ac.uk>
On 4/29/06, Alistair John Strachan <s0348365@sms.ed.ac.uk> wrote:
> On Sunday 30 April 2006 01:18, Mark Rosenstand wrote:
> > Hi,
> >
> > It seems that at least the content of the 2.6.16 tarball is world
> > writable if extracted with GNU tar as an privileged user.
> >
> > Is this on purpose in order to prove some point?
>
> Read this thread:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=113304241100330&w=2
This REALLY needs fixing. If it weren't so late right now I might have written
a filter that takes a tarball and sanitizes the permissions. I've got
good reasons
for compiling the kernel as root (when in the make, install, reboot, test loop
it's quite a timesaver).
Yes, I'm the guy who keeps trying to log in as root on ftp.kernel.org over ftp
with no password. For some bone-headed reason I keep thinking the default
username for ftp is anonymous, not the user's.
next prev parent reply other threads:[~2006-04-30 4:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 0:18 Mark Rosenstand
2006-04-30 0:48 ` Alistair John Strachan
2006-04-30 4:59 ` Joshua Hudson [this message]
2006-04-30 6:18 ` Sam Ravnborg
2006-04-30 6:47 ` Matthew Reppert
2006-04-30 16:32 ` Joshua Hudson
2006-04-30 6:53 ` Valdis.Kletnieks
2006-04-30 9:15 ` Heikki Orsila
2006-04-30 9:37 ` Willy Tarreau
2006-04-30 11:49 ` Alistair John Strachan
2006-04-30 12:36 ` Mark Rosenstand
2006-04-30 12:51 ` Alistair John Strachan
2006-04-30 17:08 ` Mark Rosenstand
2006-04-30 16:53 ` Heikki Orsila
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=bda6d13a0604292159r3187b76fg56b137816480bf2a@mail.gmail.com \
--to=joshudson@gmail.com \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®