Xref: utzoo comp.unix.aux:3733 comp.unix.admin:840
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!bourbon!dejesus
From: dejesus@bourbon.ee.tulane.edu (Francisco X DeJesus)
Newsgroups: comp.unix.aux,comp.unix.admin
Subject: Re: permissions in home directory
Message-ID: <5728@rex.cs.tulane.edu>
Date: 17 Jan 91 17:26:03 GMT
References: <5716@rex.cs.tulane.edu> <1991Jan17.114101.13022@ifi.uio.no> <1991Jan17.135129.2654@mp.cs.niu.edu>
Sender: news@rex.cs.tulane.edu
Organization: E.E. Dept., Tulane University, New Orleans, LA
Lines: 17
Sender:
Distribution:
Keywords:


    Thanks to everyone who responded to my query so quickly. The general
consensus as to why this happens is because the user owns the directory and
has permission to write (thus make changes such as removing files) in it.
Some suggested using the 'sticky bit', but I see this is not implemented in
the Unix port I'm using. Therefore the best solution (pointed out to me by
several people) would be to have the guest's home dir owned by root without
permission for guest to write, and put in a subdirectory in which the guest
CAN make his changes. This allows the dot-files to be secure and still
permits the guest user to write (after putting a 'cd subdir' in the .login
for simplicity). Again, thanks to all who posted and emailed me...

--
   ___ /      _______________________________      - Francisco X DeJesus
   |- / \/                                  \\
   ' /  /\    dejesus@bourbon.ee.tulane.edu  \\__________________________
    /         ak662@cleveland.freenet.edu    ////////////////////////////