Discussion Locked

Security and Right Assignments

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Netware Tree comprised of 4.11 and 5.1 servers. It seems that no matter what kind of file/directory access I assign to my users, it winds up that they have access to the entire tree. I have created two groups and assigned one group only Read & Filescan access to the PUBLIC Folder on the SYS volume. The second group has been assigned R,W,C,M,D rights to two folders called APPS and DATA on VOL1. There are no user except myself with individual rights assigned to them. My problem is that all users have access to everything and I need to fix this.

Please Help.

13 replies

by mablair88

Take a look at the rights assigned to the EVERYONE or PUBLIC group on the server object itself.

by tbradley

It seems you've asked 2 questions. When you say that they have access to the entire tree, does that mean that users can see all the file servers? If so, this is correct, and is a default browse right set through the "public" user.

If you're justtalking about file and directory rights on 1 file server, start looking at the following.

1. Users - though you say you're the only user with individual rights, do any users have "security equal to" set?

2. Containers - look to see if your container is assigned rights. Any user or group logging in under that container's context will have the equivalent rights.

3. Trusteees. Look to see if any groups, users, containers, etc are assigned trustee of the file server in question.

4. If you're running Zenworks, look also at
what rights are assigned to each application.
If an App is associated with a user, and that app has supervisor rights to the root, then by default, the user will also, as long as he/she is associated with that app.

by jimbb

There is a difference between file/directory access rights (Files scan, read etc.) and object rights (browse and so). File and directory rights are simple: access a file to read or write, or not.
Object rights are needed too, since a user has tofind (=browse) a server and "read" what volumes there are etc, or a printer has to "read" some properties of its printqueue and so on.
Normally everything can at least browse (=see) everything, and read a lot of things (like container login scripts), and modify a few things (like a user's own login script). If you want to, you can block a certain part of your tree, so that users/printers/whatever from another part cannot see that part. You do this for security reasons, but it has its impact,so be careful. It may be so that certain objects no longer function properly, since they cannot read the info they need, because you blocked access to a certain part.
If you're uncertain about a user's rights on some objects, right-click on such an object (like a server or so), and select "Trustees of this object". Click the "Effective rights" button, and browse to a user, to check if they have excessive rights. Most likely they'll have just "browse" and "read" and "compare", or even less.
Jim

by estebandelatorre

1.- IDENTIFYING: WHERE it came from???
PLACE A FILE IN TE ROOT OF SYS: START FILER.EXE, SELECT THE ROOT OF THE VOLUME, MANAGE FILE&DIRECTORIES, RIGHT LIST. Normally the list should be empty!
(Try the same in the sys:\public to see the difference.)
IF not Empty, remove the file system rights and you?re done.
If empty, go up a directory (e.g. server\sys:\home ) and perfom the same, and so on, till you find users or groups with specifics rights granted.

If you did not find a file system trustee, It must came from the NDS's object inherent right & trustees.
Go to NDS, select [root]and Select (Who are?) "Trustees of this object". Normaly only the Admin and perhaps you should appear in the list. (you can select the object in the list andpress DEL to remove the trustee, for example if you find here the EVERYONE group)
The trustee [PUBLIC] should be in the list too with ONLY Browse and Inheritance (without these two you can?t log in!)
If nothing strange here, go down a level, untilyou find the incorrect trustee assigment

by kevin anderson

Most common solutions were already mentioned, but also check this.

If a user (or group) has supervisor rights to the server object (In NWadmin), then they will automatically be granted full rights to all volumes on that server.

Kev.

by jcrowe

Check to see if ROOT has any *specifically assigned* rights.

We had similar problem where I work, and it turned out that ROOT had been given/granted explicit supervisor rights to the entire tree (including containers etc).

As I understand it, all users inherit (by default) rights of ROOT.

This discussion is closed to new replies.