mikshaw
Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Jan. 25 2006,02:16 |
 |
It does not, however, restrict the user to a single directory.
In the DOCUMENTATION of betaftp, there is a bit about the rights file, which sounds to me what you need.
| Quote | The `.rights' file is laid out as follows:
privilegied.file rw-r----- 0 1
(filename) (rights) (uid) (gid)
For any file not in the list, the special case `.default' is checked. If there
is no such file, _no access is permitted_, and the file will _not show up in
directory listings_. This is in fact handy in most cases, so be careful with
adding a `.default' entry. (Note that `.rights' is never influenced by a
`.default' entry, for security.)
For directory permissions, the file `dir/.rights' is checked for the entry `.'.
Yes, I know, treating them like normal directories would be great, but
remember that there is a root directory as well...
The rights are standard r, w and x for now, no setuid, setgid or sticky bit
unless we really need it. (We could perhaps need the sticky bit later.) Be
careful with the format of the `.rights' file, as everything you set in the
rights column will be copied directly to listings. Restrict yourself to
those 9 characters, no more, no less, and only use r, w, and x. |
--------------
http://www.tldp.org/LDP/intro-linux/html/index.html
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
