From owner-freebsd-current Sun May 31 14:05:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21976 for freebsd-current-outgoing; Sun, 31 May 1998 14:05:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21970 for ; Sun, 31 May 1998 14:05:13 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA23437; Sun, 31 May 1998 14:05:12 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd023410; Sun May 31 14:05:10 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id OAA13664; Sun, 31 May 1998 14:05:05 -0700 (MST) From: Terry Lambert Message-Id: <199805312105.OAA13664@usr06.primenet.com> Subject: Re: I see one major problem with DEVFS... To: michaelh@cet.co.jp (Michael Hancock) Date: Sun, 31 May 1998 21:05:05 +0000 (GMT) Cc: tlambert@primenet.com, julian@whistle.com, phk@critter.freebsd.dk, current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Jun 1, 98 03:36:36 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If a device is removed from a chroot environment, it should be impossible > > to recreate it. > > > > The reasoning should be obvious. > > Why not just control permissions on mknod? I think Julian should discuss his security model before we dive into this, but I can't see a circumstance where it would be legitimate to create a device with mknod, yet not possible to create it with the link(2) system call instead, using the template devfs. It seems to me that mknod is redundant (but mkfifo isn't). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message