From owner-freebsd-security Thu Mar 11 9:13:13 1999 Delivered-To: freebsd-security@freebsd.org Received: from brooklyn.slack.net (brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (Postfix) with ESMTP id 9BABF15297 for ; Thu, 11 Mar 1999 09:13:03 -0800 (PST) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id MAA26377; Thu, 11 Mar 1999 12:17:03 -0500 (EST) Date: Thu, 11 Mar 1999 12:17:03 -0500 (EST) From: andrewr To: freebsd-security@FreeBSD.org Cc: jbowie@slack.net Subject: Re: disapointing security architecture In-Reply-To: <199903111522.HAA00720@passer.osg.gov.bc.ca> 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 Im hoping that this thread will end soon and perhaps be brought to another context. On and off for awhile people would say someting about FreeBSDs security or lack thereof (whatever your opinion may be).. Awhile back I spoke with Jordan through email about doing an all out audit and/or a complete redesign of its "security archicture." The solution was, again: If you have people that are interested, set up a mailing list and see if you can get things started. I, unfortunately, failed on getting the mailing list up due to lack of resources at the time. 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, please email me and I will attempt to get a mailing list set up. I know this is, I think, the third time (including my single attempt) to get an active group together to do this. My role is just to hold a mailing list 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. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message