From owner-freebsd-security Wed Jul 22 06:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27621 for freebsd-security-outgoing; Wed, 22 Jul 1998 06:13:40 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27609 for ; Wed, 22 Jul 1998 06:13:35 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA13801; Wed, 22 Jul 1998 06:12:02 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: andrewr cc: Eivind Eklund , Alexandre Snarskii , Garance A Drosihn , security@FreeBSD.ORG Subject: Re: Projects to improve security (related to C) In-reply-to: Your message of "Wed, 22 Jul 1998 08:31:09 EDT." Date: Wed, 22 Jul 1998 06:12:02 -0700 Message-ID: <13797.901113122@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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 The FreeBSD core team members, by and large, already have TODO lists stretching well into next year. Do we want an audit to happen? Yes, of course. Do we have time to do all the work ourselves or even actively lead such a project in day-to-day operations? Probably not, no. We've already gone through one security officer and another has come close to resigning several times due to lack of time (these people have real jobs too, you know!) - it is a real problem which will only be mitigated by more USERS stepping up to the plate and becoming volunteers themselves. They also need someone to lead them in this effort, probably more than one person, and this is also an area where users can contribute their time and energy. Do I hear Andrew volunteering here? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message