Date: Mon, 26 Feb 1996 15:55:33 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: nate@sri.MT.net (Nate Williams) Cc: jgreco@brasil.moneng.mei.com, nate@sri.MT.net, phk@critter.tfs.com, stable@freebsd.org, current@freebsd.org Subject: Re: -stable hangs at boot (fwd) Message-ID: <199602262355.PAA15114@GndRsh.aac.dev.com> In-Reply-To: <199602262204.PAA01109@rocky.sri.MT.net> from "Nate Williams" at Feb 26, 96 03:04:06 pm
next in thread | previous in thread | raw e-mail | index | archive | help
.... > > > It's not punching any hole in the code. *ALL* of the firewall products > > > I've used (not extensive by any means) are open by default and require > > > the user to explicitly close them. If a user mis-configures the > > > firewall it's their problem in all of the other products, why is it now > > > FreeBSD's problem to make the users 'smarter'? > > > > I've never seen a firewall product that is open by default. That is an > > oxymoron. > > A firewall is *always* open by default. You determine what it is to > firewall against. All of them haven't told me how to make policy, or > force me to 'revert' behavior. Firewalls don't make policy, they > enforce policy. It is not a firewall if it is always open, it is just a plain old router :-) And per the RFC's FreeBSD can not, and does not, ship with even IP forwarding turned on. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602262355.PAA15114>