From owner-freebsd-isp Wed Dec 20 19:15:42 2000 From owner-freebsd-isp@FreeBSD.ORG Wed Dec 20 19:15:39 2000 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from hellfire.hexdump.org (h006097e24f05.ne.mediaone.net [24.128.117.73]) by hub.freebsd.org (Postfix) with ESMTP id 54EAD37B400; Wed, 20 Dec 2000 19:15:38 -0800 (PST) Received: from localhost (freebsd@localhost) by hellfire.hexdump.org (8.11.1/8.11.1) with ESMTP id eBL3IDg26691; Wed, 20 Dec 2000 22:18:13 -0500 (EST) (envelope-from freebsd@hexdump.org) Date: Wed, 20 Dec 2000 22:18:12 -0500 (EST) From: Jeff Gentry To: Kris Kennaway Cc: "Jonathan M. Slivko" , freebsd-security@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: SecureBSD? In-Reply-To: <20001220182354.G22288@citusc.usc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > That's just my personal opinion though, not any official position of > the security officer or of FreeBSD, and may not in fact reflect > reality if the documentation is inaccurate (someone told me there's > more there which is, or was, undocumented). YMMV, of course..it's > worth taking a look at to see whether it would be useful for you. I looked at it recently, and while it isn't super-duper, I do remember some of the stuff seeming useful for my purposes. The real problem tho is that SecureBSD 1.0 only supports FreeBSD 4.0. I sent them an email and they said that they were going to be soon supporting the 4.2 branch, but haven't seen anything from them yet. -- Jeff Gentry jester@hexdump.org gentrj@hexdump.org SEX DRUGS UNIX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message