From owner-freebsd-arch Sat May 6 20:44:36 2000 Delivered-To: freebsd-arch@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 3BBA337B5D8; Sat, 6 May 2000 20:44:34 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id UAA14995; Sat, 6 May 2000 20:40:52 -0700 (PDT) Message-Id: <200005070340.UAA14995@implode.root.com> To: Robert Watson Cc: freebsd-arch@FreeBSD.ORG, trustedbsd-discuss@TrustedBSD.org Subject: Re: Proposed changes to suser() In-reply-to: Your message of "Thu, 04 May 2000 10:32:06 EDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 06 May 2000 20:40:52 -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >kernel components: it is important that while introducing infrastructure >for security improvements that we don't open up security holes. > >Patches for these changes will be available shortly. I am still catching >the last few suser() calls. Third party modules making use of the suser() >call will need to be changed to set ASU properly. > >Any comments? Sounds pretty good to me, although suser_used said quickly is a bit of a tongue twister. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message