From owner-freebsd-security Wed Sep 15 19:20:28 1999 Delivered-To: freebsd-security@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C918014C0B for ; Wed, 15 Sep 1999 19:20:25 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 558D71C24; Wed, 15 Sep 1999 21:24:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 524F03817; Wed, 15 Sep 1999 21:24:31 -0400 (EDT) Date: Wed, 15 Sep 1999 21:24:31 -0400 (EDT) From: Bill Fumerola To: Brett Glass Cc: "Harry M. Leitzell" , security@freebsd.org Subject: Re: BPF on in 3.3-RC GENERIC kernel In-Reply-To: <4.2.0.58.19990915170025.048d0b00@localhost> 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 On Wed, 15 Sep 1999, Brett Glass wrote: > Maybe it's a religious issue, or maybe some utility depends on it. > But it might not be a good idea to let it be on from the get-go. > If the machine is rooted, you've got an instant packet sniffer. > I plan to turn it off on EVERY install, and I sure wish it > were that way to start. Read the archive and shut the fuck up. Let me summarize: If you have a rooted machine, you have bigger problems. If you have a sniffable network, fix that at the network level. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message