From owner-freebsd-current  Tue May 16 15:39:48 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id PAA24882
          for current-outgoing; Tue, 16 May 1995 15:39:48 -0700
Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA24838
          for <current@freebsd.org>; Tue, 16 May 1995 15:39:23 -0700
Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id XAA02840; Tue, 16 May 1995 23:35:47 +0100
Date: Tue, 16 May 1995 23:35:47 +0100
From: Mark Valentine <mark@linus.demon.co.uk>
Message-Id: <199505162235.XAA02840@linus.demon.co.uk>
In-Reply-To: Bruce Evans's message of May 16,  3:58pm
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.org
Subject: Re: MAKEDEV and device permissions
Sender: current-owner@FreeBSD.org
Precedence: bulk

> From: Bruce Evans <bde@zeta.org.au>
> Date: Tue 16 May, 1995
> Subject: Re: MAKEDEV and device permissions

> Do you think it is worth worrying about the following?
> 
> 	umask 006
> 	mknod foo c x y
> 			<----- window where group can read and write
> 			<--,
> 	chmod 600 foo	   |-- window where group may be wrong
> 			<--'
> 	chgrp baz foo

It's probably more annoying that the window is there than any real risk.

In my scheme with chmods for everything, you just set a suitably restrictive
umask at the top of the script to close all these!

I find it a good rule of thumb to stick to the order mknod/chown/chmod (and
for a lot more than just MAKEDEV).

(OK, I'll stop pushing my argument now... maybe. ;-)

		Mark.