From owner-freebsd-security  Wed Jul 22 05:26:00 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA19492
          for freebsd-security-outgoing; Wed, 22 Jul 1998 05:26:00 -0700 (PDT)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from brooklyn.slack.net (root@brooklyn.slack.net [206.41.21.102])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19487
          for <security@FreeBSD.ORG>; Wed, 22 Jul 1998 05:25:57 -0700 (PDT)
          (envelope-from andrewr@brooklyn.slack.net)
Received: from localhost (andrewr@localhost)
	by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id IAA16355;
	Wed, 22 Jul 1998 08:31:09 -0400 (EDT)
Date: Wed, 22 Jul 1998 08:31:09 -0400 (EDT)
From: andrewr  <andrewr@slack.net>
To: Eivind Eklund <eivind@yes.no>
cc: Alexandre Snarskii <snar@paranoia.ru>, Garance A Drosihn <drosih@rpi.edu>,
        security@FreeBSD.ORG
Subject: Re: Projects to improve security (related to C)
In-Reply-To: <19980722084026.45975@follo.net>
Message-ID: <Pine.NEB.3.96.980722082733.5679B-100000@brooklyn.slack.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Basically to end this thread, which Jordan requested alittle while ago, I
suggest this:
 
	If the FreeBSD core members wish to do a full scale security
audit, then, hey, make a call out for people who would like be on the
team, figure out some other way to get a group together. However, if no
security audit is wishing to take place by the core team, then, well..
Hack the code for your *own* system and have fun.

Andrew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe security" in the body of the message