From owner-freebsd-security Thu Mar 11 12:25:39 1999 Delivered-To: freebsd-security@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id 4862215364 for ; Thu, 11 Mar 1999 12:25:31 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id PAA07077; Thu, 11 Mar 1999 15:25:03 -0500 (EST) Date: Thu, 11 Mar 1999 15:25:03 -0500 (EST) From: To: andrewr Cc: freebsd-security@FreeBSD.ORG, jbowie@slack.net Subject: Re: disapointing security architecture In-Reply-To: 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 Thu, 11 Mar 1999, andrewr wrote: > So, I do extend this offer, if you are interested in doing an audit or > delve into the security implementations that FreeBSD has/does not have, Here, here. Finally, this thread takes a useful turn. ;) I am extremely interested in the security development of the FreeBSD system. I'd be willing to dedicate server resources (mailing lists, archives, shell accounts, whatever) to such a project... as others are, I'm sure. > forum for this and not much more. I know of a few people already that do > personal kernel modifications for increased security measures I encourage > you to participate. A forum for exchange of such information would be very useful, but what is the purpose of -security (announces/fixes only?). There's also the already substantial list of helpful resources provided by http://www.freebsd.org/security/security.html. Also, there was an auditing project underway (forget the URL)... I agree we need to be active and work together on this, but we don't want to waste time reinventing the wheel or redoing what other projects have already accomplished. Later, -Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message