From owner-freebsd-security Mon Mar 22 9:22: 1 1999 Delivered-To: freebsd-security@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id D6A6415122 for ; Mon, 22 Mar 1999 09:21:50 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA11311; Mon, 22 Mar 1999 18:21:18 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA37064; Mon, 22 Mar 1999 18:21:18 +0100 (MET) Date: Mon, 22 Mar 1999 18:21:17 +0100 From: Eivind Eklund To: Andrew McNaughton Cc: freebsd-security@FreeBSD.ORG, mwlucas@exceptionet.com Subject: Re: need to speak to security officer Message-ID: <19990322182117.D35449@bitbox.follo.net> References: <199903221316.IAA07200@easeway.com> <199903221537.PAA06235@aniwa.sky> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903221537.PAA06235@aniwa.sky>; from Andrew McNaughton on Tue, Mar 23, 1999 at 03:37:32AM +1200 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 23, 1999 at 03:37:32AM +1200, Andrew McNaughton wrote: > > There was an announcement a while back that the FreeBSD security officer was > resigning his post. I haven't seen any announcements since saying that we > have a new one. We have an acting security officer: Warner Losh To refer to the authorative source, the CVS logs for handbook/contrib.sgml: 1.340 Sun Feb 7 13:06:22 1999 UTC by eivind Guido don't quit being a committer just because he leaves the core team :-) Also, change Security Officer role to point at imp (that's him over in the corner - he's the scapegoat now!) > The security-officer@freebsd.org address is the correct address to use. I > gather that it goes to several people. That's correct. It reaches the entire security team, for which official up-to-date listings are currently not available. (It used to be possible to get the list of who is on the security team by running 'expn' against hub, but that route is now closed). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message