From owner-freebsd-security Mon Nov 20 15:20:14 2000 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id CFA0C37B4C5; Mon, 20 Nov 2000 15:20:09 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id SAA40131; Mon, 20 Nov 2000 18:20:06 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 20 Nov 2000 18:20:06 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Warner Losh Cc: core@freebsd.org, freebsd-security@freebsd.org Subject: Re: Item In-Reply-To: <200011202312.QAA28676@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 20 Nov 2000, Warner Losh wrote: > I think we are done with this. I don't recall what David wanted here, > but I would submit that the definition of the security officer's team > should come from the security officer and therefore we're done now with > that. Unless David wanted a statement of the powers that core has > delegated to the SO, which isn't what I recall. > > Without objection, I'll go ahead and close this later in the week. Closing it sounds great. I think David's request was that we document the procedures and processes of the Security Officer team -- in particular, who's on it, how they get there, and what responsibilities they may hold. This is probably a task for the Security Officer team to come up with, and for Core to bless after possible detail negotiation. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message