public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Troy Benjegerdes <hozer@hozed.org>
Cc: Daniel <damage@rooties.de>, linux-kernel@vger.kernel.org
Subject: Re: Kernelsources writeable for everyone?!
Date: Mon, 26 Jun 2006 15:09:10 +0200	[thread overview]
Message-ID: <449FDC76.50107@lsrfire.ath.cx> (raw)
In-Reply-To: <20060626071140.GB3359@narn.hozed.org>

Troy Benjegerdes schrieb:
> 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.

The permissions info within a tarball doesn't mean anything as long as
the file just sits there.  Only when you interpret the contents and
create files and directories they become relevant.

Tar gives you two options: A) set permissions exactly as stored in the
tar file, or B) apply the umask.  Tar archives created by git are
intended to be interpreted using option B), which is the default for GNU
tar if run as non-root.

You can interpret the tar file correctly even if you are root, you just
have to convince tar to apply the umask.

Best regards,
René

  reply	other threads:[~2006-06-26 13:09 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
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 [this message]
     [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=449FDC76.50107@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=damage@rooties.de \
    --cc=hozer@hozed.org \
    --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