From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: sandr8@crocetta.org,
Gautam Pagedar <gautam@cins.unipune.ernet.in>,
linux-kernel@vger.kernel.org
Subject: Re: can i modify ls
Date: Tue, 24 Feb 2004 11:44:38 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0402241139580.532@chaos> (raw)
In-Reply-To: <20040224163530.GA24370@louise.pinerecords.com>
On Tue, 24 Feb 2004, Tomas Szepe wrote:
> On Feb-24 2004, Tue, 15:55 +0000
> Alessandro Salvatori <a.salvatori@universitari.crocetta.org> wrote:
>
> > it's quite interesting...
>
> Actually, it's not.
>
> 1) The presence/absence of the read permission on a directory determines
> whether the user will be able to list the directory's contents.
>
> 2) The fs permission model is enforced by the kernel. Trying to impose
> additional restrictions in userspace is fragile, futile and
> an incredibly stupid idea.
If you don't have any programming tools and no access to any (like
a banking or restrictive office environment), and there is no
way to get any external executable files to run, i.e., no floppy
or no shell that could possibly access one, then writing a minimal
'ls' program that allows the clerk to see what's in her directory
might be useful.
So, it just might not be, as you say; "an incredibly stupid idea".
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-02-24 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 21:03 Gautam Pagedar
2004-02-24 11:10 ` Erik Mouw
2004-02-24 15:55 ` Alessandro Salvatori
2004-02-24 16:35 ` Tomas Szepe
2004-02-24 16:44 ` Richard B. Johnson [this message]
2004-02-24 16:59 ` Tomas Szepe
2004-02-24 18:44 ` Richard B. Johnson
2004-02-26 20:56 ` Denis Vlasenko
2004-02-25 15:01 ` Markus Klotzbuecher
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 15:04 James Lamanna
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=Pine.LNX.4.53.0402241139580.532@chaos \
--to=root@chaos.analogic.com \
--cc=gautam@cins.unipune.ernet.in \
--cc=linux-kernel@vger.kernel.org \
--cc=sandr8@crocetta.org \
--cc=szepe@pinerecords.com \
/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®