From owner-freebsd-hackers Tue Jan 28 06:09:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA15508 for hackers-outgoing; Tue, 28 Jan 1997 06:09:31 -0800 (PST) Received: from ami.tom.computerworks.net (root@AMI.RES.CMU.EDU [128.2.95.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA15503 for ; Tue, 28 Jan 1997 06:09:27 -0800 (PST) Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp (Smail3.1.29.1 #1) id m0vpEDI-0021VbC; Tue, 28 Jan 97 09:08 EST Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id IAA04275; Tue, 28 Jan 1997 08:04:43 -0600 Date: Tue, 28 Jan 1997 08:04:43 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199701281404.IAA04275@bonkers.taronga.com> To: hackers@freebsd.org Subject: Re: file locking / firewalling based on uid/gid Newsgroups: taronga.freebsd.hackers In-Reply-To: <199701031720.SAA00624@yedi.iaf.nl> References: <199701030443.UAA28355@freefall.freebsd.org> Organization: none Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199701031720.SAA00624@yedi.iaf.nl>, Wilko Bulte wrote: >And who does the chown() to allow users to get at their mail? This is only a problem because in 2.7 or so chown() for regular users was disabled to allow for the use of chown() in the "handin" program to verify assignment turn-in for users on the EECS 11/70. Later it was pointed out that you could do it by making the files created by turnin setuid, since chowning disabled the setuid bit, but by then the damage was done. The only reason for disabling chown any more is for quotas, and quotas don't work right anyway. I'd like to recommend going back to the USG semantics for chown().