From owner-freebsd-hackers Fri Jul 30 18:37:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 12AAB14EE7; Fri, 30 Jul 1999 18:37:51 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-168.bellatlantic.net [151.198.117.168]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id VAA27214; Fri, 30 Jul 1999 21:34:28 -0400 (EDT) Message-ID: <37A25361.34799F96@bellatlantic.net> Date: Fri, 30 Jul 1999 21:37:37 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Warner Losh Cc: "Brian F. Feldman" , "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: So, back on the topic of enabling bpf in GENERIC... References: <199907302342.RAA85088@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message "Brian F. Feldman" writes: > : And how about having > : if (securelevel > 3) > : return (EPERM); > : in bpf_open()? > > There are no security levels > 3. I'd be happy with > 0. This is > consistant with the meaning of "raw devices". Disabling bpf it will break rarpd (and also rbootd but it is less important). I think such a thing should be mentioned in documentation. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message