From owner-freebsd-hackers@FreeBSD.ORG  Fri Oct 31 08:28:01 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0C83416A4CE
	for <freebsd-hackers@freebsd.org>;
	Fri, 31 Oct 2003 08:28:01 -0800 (PST)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id C06AB43FB1
	for <freebsd-hackers@freebsd.org>;
	Fri, 31 Oct 2003 08:27:59 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa43123@salmon>; 31 Oct 2003 16:27:58 +0000 (GMT)
Date: Fri, 31 Oct 2003 16:27:57 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: andi payn <andi_payn@speedymail.org>
Message-ID: <20031031162757.GA56981@walton.maths.tcd.ie>
References: <1067528798.36829.2128.camel@verdammt.falcotronic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1067528798.36829.2128.camel@verdammt.falcotronic.net>
User-Agent: Mutt/1.5.3i
Sender: dwmalone@maths.tcd.ie
cc: freebsd-hackers@freebsd.org
Subject: Re: O_NOACCESS?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2003 16:28:01 -0000

On Thu, Oct 30, 2003 at 07:46:38AM -0800, andi payn wrote:
> In FreeBSD, this doesn't work; you just get EINVAL.

I believe this is because of a security problem discovered a few
years ago, where you could open a file like /dev/io for neither
read nor write but still get the special privelages associated with
having the file open.

If you were to allow people to open files without read or write
permission you'd need to fix problems like this in a different way.

	David.