From owner-freebsd-advocacy Wed Sep 20 1:10:28 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 86C9D37B423; Wed, 20 Sep 2000 01:10:25 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8K89q699019; Wed, 20 Sep 2000 01:09:53 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: cjclark@alum.mit.edu Cc: Laurence Berland , Bill Fumerola , clefevre@citeweb.net, Akbar , freebsd-advocacy@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: wats so special about freeBSD? In-Reply-To: Message from "Crist J . Clark" of "Tue, 19 Sep 2000 22:12:42 PDT." <20000919221242.O367@149.211.6.64.reflexcom.com> Date: Wed, 20 Sep 2000 01:09:52 -0700 Message-ID: <99016.969437392@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (a) "They have done the big code audit." (You got that one.) > (b) They ship a secure default. > > Not FreeBSD, nor any other open source OS I am aware of, has done > (a). FreeBSD sacrifices (b) for having some stuff work "out of the > box." I'd appreciate more specifics. I think (a) is largely a perceptual advantage since software never stands still and I have to wonder just how much of a "rolling audit" any project of a largely voluntary nature can consistently manage. As for (b), I think FreeBSD has already made some very sensible decisions there and would very much appreciate knowing just where you think it's failed to do so, using -current as a baseline if possible since there's not much point in arguing about default security policies which have already been changed. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message