From owner-freebsd-security Wed Dec 11 14:25:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14011 for security-outgoing; Wed, 11 Dec 1996 14:25:04 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA13998 for ; Wed, 11 Dec 1996 14:25:00 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vXx4u-0004Y6-00; Wed, 11 Dec 1996 15:24:36 -0700 To: Petri Helenius Subject: Re: Risk of having bpf0? (was URGENT: Packet sniffer found on my system) Cc: Brian Tao , FREEBSD-SECURITY-L In-reply-to: Your message of "Wed, 11 Dec 1996 09:16:58 +0200." <199612110716.JAA01999@silver.sms.fi> References: <199612110716.JAA01999@silver.sms.fi> <9612101452.AA21942@halloran-eldar.lcs.mit.edu> Date: Wed, 11 Dec 1996 15:24:36 -0700 From: Warner Losh Message-Id: Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199612110716.JAA01999@silver.sms.fi> Petri Helenius writes: : I think one consideration here is that to run some of the desired : functionality, like dhcpd, you need to have them. FWIW, rarpd also needs to have bpf enabled as well, or it doesn't work either. It would be nice if that wasn't the case, but it is :-(. Warner