From owner-freebsd-security  Wed Sep 15 19:20:56 1999
Delivered-To: freebsd-security@freebsd.org
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
	by hub.freebsd.org (Postfix) with ESMTP id DA5E9155AC
	for <security@FreeBSD.ORG>; Wed, 15 Sep 1999 19:20:54 -0700 (PDT)
	(envelope-from brett@lariat.org)
Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2])
	by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id UAA22557;
	Wed, 15 Sep 1999 20:20:36 -0600 (MDT)
Message-Id: <4.2.0.58.19990915201822.048e0210@localhost>
X-Sender: brett@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Wed, 15 Sep 1999 20:19:18 -0600
To: Nicholas Brawn <ncb@zip.com.au>
From: Brett Glass <brett@lariat.org>
Subject: Re: BPF on in 3.3-RC GENERIC kernel
Cc: "Harry M. Leitzell" <Harry_M_Leitzell@cmu.edu>,
	security@FreeBSD.ORG
In-Reply-To: <Pine.LNX.4.10.9909161158470.31403-100000@zipperii.zip.com.
 au>
References: <4.2.0.58.19990915170025.048d0b00@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 12:02 PM 9/16/99 +1000, Nicholas Brawn wrote:

>Come on people, this issue is long past dead and buried. It is a simple
>matter to [dis|enable] BPF in the kernel. 

Right now (correct me if I'm wrong, please) it seems to require recompiling
the kernel.

--Brett



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message