From owner-cvs-all@FreeBSD.ORG  Fri Sep 26 11:46:21 2003
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AE3C216A4BF; Fri, 26 Sep 2003 11:46:21 -0700 (PDT)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2EAFA44003; Fri, 26 Sep 2003 11:46:20 -0700 (PDT)
	(envelope-from sam@errno.com)
Received: from melange.errno.com (melange.errno.com [66.127.85.82])
	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h8QIkG0x055879
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 26 Sep 2003 11:46:19 -0700 (PDT)
	(envelope-from sam@errno.com)
Date: Fri, 26 Sep 2003 11:46:21 -0700
From: Sam Leffler <sam@errno.com>
To: Nate Lawson <nate@root.org>,
	"Jeroen C.van Gelderen" <jeroen@vangelderen.org>
Message-ID: <1195731400.1064576781@melange.errno.com>
In-Reply-To: <20030926112233.X65171@root.org>
References: <25426A04-F046-11D7-9CBF-00039375644C@vangelderen.org>
 <20030926112233.X65171@root.org>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/etc/defaults devfs.rules
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2003 18:46:22 -0000

> My basic point is that this change may make any hardware weaknesses that
> we don't address more fatal by giving hostile users access to the
> hardware.  I don't object to the change but just wanted to question
> whether we've written our drivers and evaluated our hardware with this
> threat model in mind.

The crypto support hasn't been written with that in mind.  I'd welcome
critique and/or fixes.

	Sam