public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Salvatori <a.salvatori@universitari.crocetta.org>
To: Gautam Pagedar <gautam@cins.unipune.ernet.in>,
	linux-kernel@vger.kernel.org
Subject: Re: can i modify ls
Date: Tue, 24 Feb 2004 15:55:46 +0000	[thread overview]
Message-ID: <403B7402.2000008@universitari.crocetta.org> (raw)
In-Reply-To: <005601c3fd75$1c681510$8c01080a@crayii>

a directory is a file. it has got its own rights, that are rights 
referred to that particular file. maybe you should not allow people to 
use ls and make them use your own ls_patched but they still could give a 
"echo *" command which would be expanded by bash or other shells... 
so... what could you do with that? are you going to patch any shell you 
give access to?
let me know, it's quite interesting...
cheers
Alessandro Salvatori

Gautam Pagedar wrote:

>Hello Everyboy.
>   i am new to this mailing list, so please bear with me if i don't follow
>certain rules till i get used to it.  I am a research student and currently
>working on a project to tweak the working of 'ls' command depending on my
>requirement. I have observed that 'ls' show ALL THE FILES and DIRECTORIES in
>a particular location even though a user has no access rights to it. I want
>to hide all
>such files for that particular user.
>
>The Algorithm i beleive should work like this when an 'ls' command is
>called.
>
>1. Check the current directory.
>2. Extract the files or directory to be displayed.
>3. Check the user permissions for these files.
>4. Display only those files wher user had either read, write or execute
>access for all owner,group and others.
>
>I have found out that 'ls' uses getdents64() system call for gathering the
>directory information. How do i move ahead from here.
>
>Regards,
>Gautam Pagedar
>Centre for Information and Network Security
>
>
>
>
>
>
>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>


  parent reply	other threads:[~2004-02-24 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 21:03 can i modify ls Gautam Pagedar
2004-02-24 11:10 ` Erik Mouw
2004-02-24 15:55 ` Alessandro Salvatori [this message]
2004-02-24 16:35   ` Tomas Szepe
2004-02-24 16:44     ` Richard B. Johnson
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=403B7402.2000008@universitari.crocetta.org \
    --to=a.salvatori@universitari.crocetta.org \
    --cc=gautam@cins.unipune.ernet.in \
    --cc=linux-kernel@vger.kernel.org \
    --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