From owner-freebsd-security Thu Dec 12 07:06:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA15925 for security-outgoing; Thu, 12 Dec 1996 07:06:38 -0800 (PST) Received: from black.gensys.com (black.gensys.com [206.109.98.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA15918 for ; Thu, 12 Dec 1996 07:06:35 -0800 (PST) Received: (from jhupp@localhost) by black.gensys.com (8.7.5/8.6.12) id JAA23109; Thu, 12 Dec 1996 09:01:47 -0600 (CST) From: Jeff Hupp Message-Id: <199612121501.JAA23109@black.gensys.com> Subject: Re: Risk of having bpf0? (was URGENT: Packet sniffer found on my system) To: lithium@cia-g.com (Stephen Fisher) Date: Thu, 12 Dec 1996 09:01:46 -0600 (CST) Cc: dg@root.com, msmith@atrad.adelaide.edu.au, taob@io.org, freebsd-security@freebsd.org In-Reply-To: from "Stephen Fisher" at Dec 12, 96 07:32:56 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stephen Fisher bound electrons in the following form:: : : Can't the hacker just recompile the kernel with bpf support and then use : it, though? : I notice when one of my systems reboots. Leaving bpf in a public machine connected to the internet is a bit like leaving a loaded gun in a public place ~ you are largely responsible for what happens. -- Jeff Hupp | While ignorance my be an | PGP Public Key | | explanation, stupidity | available at | | is often the reason. | http://gensys.com |