Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!princeton!allegra!ulysses!sfmag!sfsup!mpl From: mpl@sfsup.UUCP Newsgroups: comp.os.minix Subject: Re: SETUID on mkdir and rmdir Message-ID: <1594@sfsup.UUCP> Date: Mon, 6-Jul-87 11:08:59 EDT Article-I.D.: sfsup.1594 Posted: Mon Jul 6 11:08:59 1987 Date-Received: Wed, 8-Jul-87 03:04:30 EDT References: <8707030732.a029212@Louie.UDEL.EDU> Organization: AT&T-IS, Summit N.J. USA Lines: 25 Summary: wrongo In article <8707030732.a029212@Louie.UDEL.EDU>, ESC1332@ESOC (K.Keyte) writes: > > Does everyone have SETUID on their mkdir and rmdir? Standard UNIX does > not, as the mkdir and rmdir are just normal file operations. I don't know what you consider "standard", but here at AT&T, we put 'em on our mkdir and rmdir. > In MINIX, if > SETUID is on it means that any user has the permission to create and delete > directories anywhere is the file system. I don't have my MINIX source with me, but I'd be surprised. Mkdir and rmdir use access(2) to check permissions before they let the user do what he's trying to do. > I've tried, however, taking the > SETUID bit off, but I can't seem to create ANY directories from normal user > accounts in this state. > > Has anyone any experience with this aspect, or can anyone advise me what the > situation should be? that's my experience, and my advice is put on the s-bits. That's what they're there for.