12 lines
31 KiB
Plaintext
12 lines
31 KiB
Plaintext
en·vÅos NSPROTECTION
|
||
2
|
||
|
||
4
|
||
|
||
1
|
||
|
||
NSPROTECTION
|
||
1
|
||
|
||
4
|
||
|
||
By: Bill van Melle (vanMelle@Xerox.com)
|
||
INTRODUCTION
|
||
The module NSPROTECTION provides a tool that enables you to easily change the protection of files and directories on Xerox NS file servers.
|
||
To install the module, load the file NSPROTECTION.LCOM. Also, Your NS file server must be running Services release 10.0 or later.
|
||
THE PROTECTION MECHANISM
|
||
An NS File Server maintains a protection for each file and (sub)directory on the server. In most cases, the protection is not specified explicitly, but rather is inherited from a file's parent directory, making it easy to maintain consistent protection over an entire branch of the file system hierarchy.
|
||
The protection is specified as a set of pairs <access rights, name>. The name can be the name of an individual user or a group. The name can also be a pattern of the restricted form *:domain:organization, *:*:organization, or *:*:*. The access rights granted to any particular user are the most general of those in the pairs that match the user's name (by exact match, pattern or membership).
|
||
The following five kinds of access rights are independently specified (the term "file" here can also denote a directory in the places where that makes sense):
|
||
Read The user may read the file's content and attributes. In the case of a directory, the user may enumerate files in it.
|
||
Write The user may change the file's content and attributes, and may delete the file. In the case of a directory, the user may change the protection of any of the directory's immediate children.
|
||
Add (Applies only to directories) The user may create files in the directory (i.e., add children).
|
||
Delete (Applies only to directories) The user may delete files from the directory (i.e., remove children).
|
||
Owner The user may change the file's access list.
|
||
In the case of directories, it is also possible to independently specify the directory's own protection and the protection that its children inherit by default. In most cases, the latter simply defaults to the former, and it is usually best to keep it that way for simplicity. However, there might conceivably be cases where, for example, you would want a user to be able to read the files in a directory, but not be able to enumerate it, or vice-versa.
|
||
Note that there can be problems when giving a more lenient protection to a file or directory than to its parents, depending on what software is going to be used to gain access to the file. For example, if your default directory protection grants access only to you, and you want to allow a user to read a particular file stored in your directory, then you can change the protection on just that file to allow Read access. However, the user will have to know the exact name of the file in order to read it, since she won't be able to enumerate the directory to search for the file. Specifying the exact file name works fine from Lisp, but other software that gets to a file by starting at the top and working its way down through the hierarchy would be unable to get to the file.
|
||
USER INTERFACE
|
||
To use the tool, select "NS Protection" from the background menu (if your menu has a "System" item, it's a subitem underneath it), or call the function (NSPROTECTION). You are prompted for a place to position the tool's window. Be sure to leave space below the window for the protection information that will follow.
|
||
|