From owner-freebsd-hackers Wed Nov 27 15:28:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22323 for hackers-outgoing; Wed, 27 Nov 1996 15:28:18 -0800 (PST) Received: from ami.tom.computerworks.net (AMI.RES.CMU.EDU [128.2.95.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA22318 for ; Wed, 27 Nov 1996 15:28:16 -0800 (PST) Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp (Smail3.1.29.1 #1) id m0vStOW-0021WDC; Wed, 27 Nov 96 18:27 EST Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id RAA17937; Wed, 27 Nov 1996 17:24:19 -0600 Date: Wed, 27 Nov 1996 17:24:19 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199611272324.RAA17937@bonkers.taronga.com> To: hackers@freebsd.org Subject: Re: looking for an idea Newsgroups: taronga.freebsd.hackers In-Reply-To: <199611260923.AA137920219@ws2301.gud.siemens.co.at> References: <199611251840.SAA21376@right.PCS> Organization: none Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199611260923.AA137920219@ws2301.gud.siemens.co.at>, Hr.Ladavac wrote: >> How about having the client create a file of mode 000, and then pass that >> open file descriptor back to the server? Since it's mode 000, only the >> owner of the file could have opened it (or chowned it to 000). The file can >> either be created randomly by the client, or specified by the server. >Won't work on SysV. Anyone can chown(2) his own files to anyone else. >The funny thing about it is that they claim they support quotas :) It will if you insist the file is chmod +s. The only person who can create a setuid file owned by user "A" is user "A".