Date: Mon, 25 Sep 2000 09:41:29 -0400 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Joseph Scott <joseph.scott@owp.csus.edu> Cc: Wes Peters <wes@softweyr.com>, Bill Fumerola <billf@chimesnet.com>, cjclark@alum.mit.edu, freebsd-advocacy@FreeBSD.ORG Subject: Re: wats so special about freeBSD? Message-ID: <20000925094129.A30394@blackhelicopters.org> In-Reply-To: <Pine.BSF.4.21.0009250611290.196-100000@pebkac.owp.csus.edu>; from joseph.scott@owp.csus.edu on Mon, Sep 25, 2000 at 06:18:28AM -0700 References: <39CC3AEB.3D768A0E@softweyr.com> <Pine.BSF.4.21.0009250611290.196-100000@pebkac.owp.csus.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> "if you want to install a secure system and don't know what you're doing > ..." Unfortunately, that's life in IT nowadays. I'm the support management dude for a consulting company. We run NT, AIX, Solaris, AS/400, and a few other things, not to mention the programs than run on them. The folks under me are decent, but not what I'd call "expert." FreeBSD is fairly easy to lock down, but I'd feel *far* better if I knew everything on all my boxes was shut down by default. I do a "netstat -na" on a Solaris machine and cry. Many UNIXes make it difficult to identify what's running where. Should the company devote the hundreds of man-hours necessary to learn exactly what is running everywhere and determine how necessary it is? Yep. Are they going to? Nope. Can we even *hire* some of those experts here in Detroit? Nope. All I can say is, thank God for my FreeBSD firewall. All I have to worry about is my inside users. :) ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000925094129.A30394>