Re: can i modify ls

[Alessandro Salvatori]

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@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/