From owner-freebsd-current Tue Nov 23 12:24: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 27D05153BE for ; Tue, 23 Nov 1999 12:23:56 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA46984; Tue, 23 Nov 1999 15:23:23 -0500 (EST) Date: Tue, 23 Nov 1999 15:23:23 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: FreeBSD security auditing project. In-Reply-To: <199911231905.VAA80946@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Mark Murray wrote: > I am prepared to provide a (semi-)automatic tool that folks can > submit their efforts to. (Yes, this is a group effort, we all need to > get involved and donate our Copious Free Time. All the time that is > currently invested in flamewars would be better spent here, *hint* > *hint*.) The tool will be web-based and will give a good idea of > progress, so we can even turn it into a sort of competition. > Need volunteers, eh? I can be suckered in to helping in regards to building the web-based database for keeping track of the effor's progress. I may be no security expert, but I can build database-driven web sites (I should...it's my day job ;) ). Let me know what I can do to help. > > I'll get a mailing list going if this is deemed necessary. > freebsd-security? :) -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message