After reading the following page to update myself on how NTFS file, folder, and share permissions work, I am left with a few questions and hope to receive some answers on this group:
The page states that when a permission is dimmed it means such permission is inherited from a parent object (I guess in the case of folders this could mean the parent folder, but what would this mean in the case of files?).
What is the difference between a user and a contact (as mentioned at the top of the given page)?
On my system, besides the basic permissions Full Control, Modify, Read & Execute, List Folder Contents, Read, and Write, there is another permission listed in the access control list of various files, namely the "special authorization" permission. What is this, what is it used for, where does it come from, and why is it not described on any of the various sites that explain attributes pertaining to NTFS files, folders, and shares?
The page states that read permission is needed to run scripts and execute permission is not needed for these on Windows. Presumably by scripts we mean any file which is interpreted as opposed to compile, but with the sheer multitude of file types which can be run on Windows systems, how would I know which ones actually needed execute permissions and which ones didn't?
In the permissions table on the link I posted, is there a typo pertaining to the List folder Contents permission for folders (I didn't think this implied an execute permission)?
Thank you for your help.