From: Nick Warne <nick@linicks.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@osdl.org>,
Felipe Alfaro Solana <felipe.alfaro@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: chmod 111
Date: Sat, 18 Mar 2006 12:42:24 +0000 [thread overview]
Message-ID: <200603181242.24619.nick@linicks.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0603172243460.829@yvahk01.tjqt.qr>
On Friday 17 March 2006 21:44, Jan Engelhardt wrote:
> >Yep, I agree whole heartily. I should have stressed the "little" part
> >in the above quote. "might make your system a __little__ more secure.".
>
> -rws--x--x 1 root root 1847788 Sep 16 14:58 /usr/X11R6/bin/Xorg
>
> I never could figure out what this permission mask was good for.
Yes, my post was initiated by a question in this months RH magazine - somebody
asked why 'finger' on RH systems was chmod 0711 and how/why ordinary users
could still run it. Shadowman didn't know and I was stumped too.
Nick
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
next prev parent reply other threads:[~2006-03-18 12:42 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
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 [this message]
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=200603181242.24619.nick@linicks.net \
--to=nick@linicks.net \
--cc=felipe.alfaro@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.