From: Nick Warne <nick@linicks.net>
To: "Felipe Alfaro Solana" <felipe.alfaro@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: chmod 111
Date: Fri, 17 Mar 2006 18:11:01 +0000 [thread overview]
Message-ID: <200603171811.01963.nick@linicks.net> (raw)
In-Reply-To: <6f6293f10603171007vbf752e5n8a3d6f2d65e0a1e7@mail.gmail.com>
On Friday 17 March 2006 18:07, Felipe Alfaro Solana wrote:
> > I shouldn't be able to execute 'ls' as I can't read it, shouldn't it?
>
> Nop... you can execute binaries even if the read permission is not
> granted. Note that I said "binaries". Shell script files need read and
> execute permission, since they must be read by a shell interpreter in
> order to get executed.
Hi Felipe,
First, apologies as this isn't kernel issue (but related, I suppose).
Yes, I see now after much messing about. Why then are most binaries chmod
755? Who would need (why) to read a [system] binary?
Nick
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
next prev parent reply other threads:[~2006-03-17 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 17:46 chmod 111 Nick Warne
[not found] ` <6f6293f10603171007vbf752e5n8a3d6f2d65e0a1e7@mail.gmail.com>
2006-03-17 18:11 ` Nick Warne [this message]
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
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=200603171811.01963.nick@linicks.net \
--to=nick@linicks.net \
--cc=felipe.alfaro@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