From: Bodo Eggert <7eggert@elstempel.de>
To: artusemrys@sbcglobal.net, oshua Hudson <joshudson@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernelsources writeable for everyone?!
Date: Mon, 26 Jun 2006 01:29:21 +0200 [thread overview]
Message-ID: <E1Fue2x-0001bp-12@be1.lrz> (raw)
In-Reply-To: <6rL7C-4oS-41@gated-at.bofh.it>
Matthew Frost <artusemrys@sbcglobal.net> wrote:
> Joshua Hudson wrote:
>> I feel like asking how they initially get set to world-writable. To me
>> it means that the tree that is being tarred up for distribution is
>> world-writible. I sure hope that it is a single-user box.
>> -
>
> Yeah. Having said, "Take advice", I'm also curious as to just the
> why/how of the current configuration and the work patterns that create
> it. I get the impression that there *is* a reason for it, because if it
> were just a security issue, I can't see this much resistance to changing
> it. Sane tar permissions and sensible usage aside.
The reason is the same for which an application SHOULD NOT impose stricter
permissions than 0666 without a reasonon open/create: It's supposed to
honor the umask, imposing a restriction is none of it's busines.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
http://david.woodhou.se/why-not-spf.html
next parent reply other threads:[~2006-06-25 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2006-06-26 13:09 ` Rene Scharfe
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=E1Fue2x-0001bp-12@be1.lrz \
--to=7eggert@elstempel.de \
--cc=7eggert@gmx.de \
--cc=artusemrys@sbcglobal.net \
--cc=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
Powered by JetHome