From: Troy Benjegerdes <hozer@hozed.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Daniel <damage@rooties.de>, linux-kernel@vger.kernel.org
Subject: Re: Kernelsources writeable for everyone?!
Date: Mon, 26 Jun 2006 02:11:40 -0500 [thread overview]
Message-ID: <20060626071140.GB3359@narn.hozed.org> (raw)
In-Reply-To: <20060624181702.GG27946@ftp.linux.org.uk>
On Sat, Jun 24, 2006 at 07:17:02PM +0100, Al Viro wrote:
> On Sat, Jun 24, 2006 at 08:00:50PM +0200, Daniel wrote:
> > Hi,
> > may be this was reported/asked 999999999 times, but here ist the 1000000000th:
> >
> > I have downloaded linux-2.6.17.1 10 min ago and I noticed that every file is
> > writeable by everyone. What's going on there?
>
> You are unpacking tarballs as root and preserve ownership and permissions.
> Don't.
While it is true that users generally shouldn't be unpacking tarballs as root,
It seems rather monumentally stupid for a trusted source for a critical
system component (aka, kernel.org) to be distributing tarballs like
this.
How hard is it really to make the git tarball export script set sane
owner (root) and permissions (644/755) on files and directories?
next prev parent reply other threads:[~2006-06-26 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 18:00 Daniel
2006-06-24 18:05 ` Avuton Olrich
2006-06-24 18:14 ` Rene Scharfe
2006-06-24 18:17 ` Al Viro
2006-06-25 1:20 ` Mark Rosenstand
2006-06-25 5:38 ` Matthew Frost
2006-06-25 20:09 ` Joshua Hudson
2006-06-25 22:16 ` Matthew Frost
2006-06-25 23:05 ` Matthew Frost
2006-06-29 6:11 ` Junio C Hamano
2006-06-29 14:38 ` Bill Davidsen
2006-06-26 7:11 ` Troy Benjegerdes [this message]
2006-06-26 13:09 ` Rene Scharfe
[not found] <6rkK4-7Do-1@gated-at.bofh.it>
[not found] ` <6rkTT-7OS-23@gated-at.bofh.it>
[not found] ` <6rrsb-vZ-5@gated-at.bofh.it>
[not found] ` <6rvFs-6xp-3@gated-at.bofh.it>
[not found] ` <6rJ5L-1n7-3@gated-at.bofh.it>
[not found] ` <6rL7C-4oS-41@gated-at.bofh.it>
2006-06-25 23:29 ` Bodo Eggert
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=20060626071140.GB3359@narn.hozed.org \
--to=hozer@hozed.org \
--cc=damage@rooties.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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®