From: Matthew Frost <artusemrys@sbcglobal.net>
To: Mark Rosenstand <mark@borkware.net>
Cc: Al Viro <viro@ftp.linux.org.uk>, Daniel <damage@rooties.de>,
linux-kernel@vger.kernel.org
Subject: Re: Kernelsources writeable for everyone?!
Date: Sun, 25 Jun 2006 00:38:54 -0500 [thread overview]
Message-ID: <449E216E.8010508@sbcglobal.net> (raw)
In-Reply-To: <1151198452.6508.10.camel@mjollnir>
Mark Rosenstand wrote:
> On Sat, 2006-06-24 at 19:17 +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?
>
> It's an abusive way of telling people to not extract the kernel sources
> as root. Surely if they don't follow the recommended workflow, their box
> deserve to be rooted.
>
No, the inevitable flame war here is the abusive way of telling people
not to extract the kernel sources as root. This argument boils down to
a fundamental disjunct: trust people to handle security of their own box
their own way, with full knowledge of how their tools work, or assume
that they aren't intelligent enough to use tools sanely and securely,
and handicap so they don't have to. The latter, much as it is not seen
this way, is the abusive philosophy. The former trusts the user.
Yes, there's a learning curve. There is always a learning curve. Never
expect there not to be a learning curve.
The kernel archive is foremost an archive of a working directory. The
recommended workflow is sane, and is designed around the limitations of
tools sensibly designed for a wide range of purposes, not foremost of
which is kernel compilation.
Please learn to take advice. It tends to be intended for your benefit,
and is generally more useful when not viewed as a personal affront.
>> You are unpacking tarballs as root and preserve ownership and permissions.
>> Don't.
>
> Preserving ownership and permissions is the default behaviour for GNU
> tar when running as root. Other implementations require the -p option.
Matt
next prev parent reply other threads:[~2006-06-25 5:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 18:00 Kernelsources writeable for everyone?! 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 [this message]
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
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=449E216E.8010508@sbcglobal.net \
--to=artusemrys@sbcglobal.net \
--cc=damage@rooties.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@borkware.net \
--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