|
Posted by Roger Abell [MVP] on April 25, 2008, 11:53 pm
Please log in for more thread options > Here's an example of a result I didn't expect: on the security
> properties for a folder, inheritance is turned off and "Users" are
> granted all permissions except full control (i.e. except "delete
> subfolders", "change permissions", and "take ownership"). They are not
> explicity denied any permission. Then by an oversight "Administrators"
> are left off of the "permission entries" (i.e. the list of groups with
> permissions granted or denied) for the folder. The result is that a
> user in both the "Users" and "Administrators" groups is not allowed to
> even list the contents of the folder.
>
> When the security properties for the same folder are reversed
> ("Administrators" are granted full control and "Users" are not listed
> in the "permission entries") the same user (a member of both the
> "Users" and "Administrators" groups) has full control of the folder.
>
> I would have expected this user to have the permissions of whichever
> group was granted permissions to the folder.
>
> I doubt I'll be able to understand all of this through examples. Is
> there a document that lays out all of the rules?
>
I cannot point you to a specific doc (it has been a long time since
I have looked for that in a doc) but I am fairly certain you could
find a statement in the resource kit.
There are no NTFS rules other than what I stated in first reply.
If there are no denies involved then an account has the sum of all
grants made to it for an item.
From what you have said there must be something else involved
as if the account tested is member of Users and Administrators
and an attempt is made to access a folder on which all is granted
to Users except the three items you mentioned, then they should
be able to list the folder content (this is being done via direct
login, right? It's not via a mapped share - as if a share is involved
then the share level permissions act as an upper bound on what
may be done : in this case if the share permits Administrators
but not Users then what you report would make sense as the
correct behavior).
Roger
|