From: Tomas Szepe <szepe@pinerecords.com>
To: "Richard B. Johnson" <root@chaos.analogic.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 17:59:43 +0100 [thread overview]
Message-ID: <20040224165943.GB24370@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0402241139580.532@chaos>
On Feb-24 2004, Tue, 11:44 -0500
Richard B. Johnson <root@chaos.analogic.com> wrote:
> 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 what is it exactly that prevents the admin from running /bin/chmod
in the setup you're describing?
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2004-02-24 17:00 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
2004-02-24 16:59 ` Tomas Szepe [this message]
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=20040224165943.GB24370@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=gautam@cins.unipune.ernet.in \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=sandr8@crocetta.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
all inboxes | Powered by JetHome®