Re: IFS Authorities

[Patrick Botz <pcbotz@xxxxxxxxx>]

WARNING: The following is based entirely on memory. This is how I recall it 
works...Testing this would be prudent thing to do :-)

If my memory is correct, you should only need *X to main and subdir1 and 
depending on the behavior you want either *R or *RX to target.

*X on a directory provides the ability to "search" the directory (e.g. *X 
lets you list the contents of a directory). You must be able to search a 
directory to traverse into a subtree of that directory.

*X on file lets you "execute" that file...if it's not executable, as I 
recall, it really has no meaning.

*R on a directory lets you read the contents of the directory -- meaning if 
you know a file name in the directory you can list that file and determine 
if it exists or not.

*R on a file in the directory means you can read that file.

I assume that you are talking about "public authority" and not private 
authorities at this point.
So, if your program knows the pathname to the file and doesn't need to list 
the contents of "target," then I would put *X on the main and subdir1. *R on 
target and *R on the file it needs to read....


On 22 Apr 2005 13:08:52 -0400, R Bruce Hoffman <
bruce.hoffman@xxxxxxxxxxxxxxxxx> wrote:
> 
> On Fri, 2005-04-22 at 12:40, Jon Paris wrote:
> > My brain has always had problems understanding the screwy world of IFS
> > security and today it is being slowed down further by flu - so be 
> merciful
> > please.
> >
> > I have the following IFS directory structure 
> main/subdir1/target/xxxx.xxx
> >
> > I need to ensure full access to all files within the target directory - 
> but
> > _not_ allow anything other than read access for all intervening levels.
> >
> > Can someone refresh my addled brain please - is it *RX I need for main 
> and
> > subdir1?
> 
> Yes, but you should try the right profile first... <LOL>
> 
> 
> >
> > Jon Paris
> > Partner400
> >
> > www.Partner400.com <http://www.Partner400.com>
> > www.RPGWorld.com <http://www.RPGWorld.com>
> --