From owner-freebsd-questions  Fri Jan 19 10:26:45 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA03090
          for questions-outgoing; Fri, 19 Jan 1996 10:26:45 -0800 (PST)
Received: from gdi.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA03085
          for <questions@freebsd.org>; Fri, 19 Jan 1996 10:26:43 -0800 (PST)
Received: (from dwhite@localhost) by gdi.uoregon.edu (8.6.12/8.6.12) id KAA01052; Fri, 19 Jan 1996 10:27:21 -0800
Date: Fri, 19 Jan 1996 10:27:21 -0800 (PST)
From: Doug White <dwhite@riley-net170-164.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: Anthony Hill <ahill@interconnect.com.au>
cc: questions@freebsd.org
Subject: Re: consequences of `bpfilter' pseudo-device
In-Reply-To: <Pine.BSI.3.91.960119225519.20104B-100000@tulpi.interconnect.com.au>
Message-ID: <Pine.BSF.3.91.960119102439.1005C-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
Precedence: bulk

On Fri, 19 Jan 1996, Anthony Hill wrote:

> May I ask, what are the legal and administrative consequences of enabling 
> bpfilter ?

bpfilter gives you the opportunity to look inside all the packets coming 
across your local net.  Not exactly great for security.  Plus, you can 
see where packets are coming from and where they are going, so you can 
see that your boss browses www.playboy.com in his spare time, for 
example.  

Basically, it's a privacy issue.  Great for debugging, but also for 
peeking in on what other people are doing.

Doug White                              | University of Oregon  
Internet:  dwhite@gladstone.uoregon.edu | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major