From: Helge Hafting <helgehaf@aitel.hist.no>
To: Nick Warne <nick@linicks.net>
Cc: Felipe Alfaro Solana <felipe.alfaro@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: chmod 111
Date: Sat, 18 Mar 2006 15:09:36 +0100 [thread overview]
Message-ID: <20060318140936.GA1797@aitel.hist.no> (raw)
In-Reply-To: <200603171811.01963.nick@linicks.net>
On Fri, Mar 17, 2006 at 06:11:01PM +0000, Nick Warne wrote:
>
> Yes, I see now after much messing about. Why then are most binaries chmod
> 755? Who would need (why) to read a [system] binary?
The system binaries are normally not considered secret. (You can
download source for any of them.) So why prevent anyone from reading them?
Reading the binaries are convenient for copying them, or backing them
up. This don't happen often, but there is no need to make life difficult
as these files contain no secrets.
Similiarly - lots of files in etc could be made root only. But
there is no need. Making more stuff root only also force people to
use root more often, which is a bad thing.
Helge Hafting
next prev parent reply other threads:[~2006-03-18 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 17:46 Nick Warne
[not found] ` <6f6293f10603171007vbf752e5n8a3d6f2d65e0a1e7@mail.gmail.com>
2006-03-17 18:11 ` Nick Warne
2006-03-17 18:26 ` Steven Rostedt
2006-03-17 18:43 ` Linus Torvalds
2006-03-17 18:55 ` Steven Rostedt
2006-03-17 21:44 ` Jan Engelhardt
2006-03-18 12:42 ` Nick Warne
2006-03-17 19:38 ` Phillip Susi
2006-03-17 20:11 ` Linus Torvalds
2006-03-17 20:27 ` Nick Warne
2006-03-17 20:56 ` Willy Tarreau
2006-03-18 14:09 ` Helge Hafting [this message]
2006-03-17 18:12 ` Joshua Hudson
[not found] ` <441AFBF5.7010009@tlinx.org>
2006-03-17 18:14 ` Nick Warne
2006-03-17 18:18 ` Phillip Susi
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=20060318140936.GA1797@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=felipe.alfaro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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®