On 23 Jan 2003 at 11:18, Willie Vu wrote: > I want to setup permissions so that: > > 1. each user (say John) has his own /files/<user name> directory. Only he > and root has write permission. > 2. John is allowed to grant read permission to other users (say Mary). > 3. The number of users who can share directories are dynamic. So, new users > (Joe, Peter) will be created after permissions are set up. > > The namespace looks like this: > > / > - files > -- john (root and john has read/write permission; mary has read permission) > - users > -- root > -- john > -- mary > > More users will be created in the future. I want to make sure no new users > have read permission to /files/john. So, I tried adding a negative > permission to /files/john, i.e. (/files/john, /users, /actions/read, > negative). The problem is that even john and root has no read permission to > /files/john. The reason is that If Slide finds a permission conflict on the > same node, the negative permission prevails. I have do not specify > permission explicitly, it seems like everyone has /actions/read to > /files/john. > > My question is, how do I setup permissions so that a node is only readable > by persons whom are granted /actions/read explicitly and no one else, > including new users, have /actions/read to the node? > Permissions are a difficult topic...
Grant /actions/read on / and /files to /users NOT inheritable. Then grant inheritable permission on /files/john for /users/john. Grant /actions on / to root inheritable. How do you protect your /history? > > -- > Willie Vu > > Andreas -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
