From owner-freebsd-security Thu Aug 12 11: 2:22 1999 Delivered-To: freebsd-security@freebsd.org Received: from slack.net (brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (Postfix) with SMTP id 9ABFA14E91 for ; Thu, 12 Aug 1999 11:02:11 -0700 (PDT) (envelope-from andrewr@slack.net) Received: (qmail 3498 invoked by uid 1077); 12 Aug 1999 17:57:05 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Aug 1999 17:57:05 -0000 Date: Thu, 12 Aug 1999 13:57:05 -0400 (EDT) From: andrewr To: Tom Brown Cc: "'freebsd-security@freebsd.org'" Subject: Re: "Secure-FreeBSD" Idea In-Reply-To: <01BEE4A8.6FE3EEC0@beetroot.securify.com> 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 I believe myself as well as a few others have had this idea and, basically, when we attempted to start such a project up, many people said "Yah,sure Id help"...but the bottom line is, we're all too busy ;) Andrew On Thu, 12 Aug 1999, Tom Brown wrote: > HI, > > Just come back from "websec" which was a bit dull, but I did get the feeling whilst fighting off the sleep that there is a really good opening for a quality secure O/S. > > Now realistically all this would have to be is a really anal installation process, forcing the user to positively select services such as ftp,telnet, sendmail etc. So if you don't select anything, you can't much. It would also have carefully set UMASKS and probably come with some easy way to get the user to set-up tripwire and ipfw for example. > > I suspect that most of the readers of this list spend a fair amount of time going through the same laborious process of tying down each server they built. How about we pools this vast collection of procedures together and try to build some kind of a security release. We all know (well at least I hope we do!) what a solid O/S FreeBSD is, wouldn't this be the ideal opportunity, to push the OS further into the public eye? > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message