From owner-cvs-src@FreeBSD.ORG  Thu Mar  4 14:08:09 2004
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AE2A516A4CE; Thu,  4 Mar 2004 14:08:09 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 23BE643D31; Thu,  4 Mar 2004 14:08:09 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i24M88kj099034;
	Thu, 4 Mar 2004 15:08:08 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Thu, 04 Mar 2004 15:08:11 -0700 (MST)
Message-Id: <20040304.150811.124827383.imp@bsdimp.com>
To: nate@root.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20040304100856.Y24532@root.org>
References: <20040304170353.64D4F16A4D4@hub.freebsd.org>
	<20040304100856.Y24532@root.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: takawata@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
cc: cvs-src@FreeBSD.org
Subject: Re: cvs commit: src/usr.sbin/acpi/acpiconf acpiconf.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2004 22:08:09 -0000

In message: <20040304100856.Y24532@root.org>
            Nate Lawson <nate@root.org> writes:
: I am concerned about this change since being able to open a descriptor
: read-only implies they can do ioctl, which means they can also suspend the
: system.  If we have to do this, we might have to go the setgid route
: although I don't necessarily want to deal with the security implications
: of that.  Users can get battery status through apm(8) but not battery
: info.

ioctl can be made to require a write open.  That's what the apm ioctls
required, except for battery status.

Warner