From owner-freebsd-questions Fri Jan 19 04:06:03 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10921 for questions-outgoing; Fri, 19 Jan 1996 04:06:03 -0800 (PST) Received: from tulpi.interconnect.com.au (root@tulpi.interconnect.com.au [192.189.54.18]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA10835 for ; Fri, 19 Jan 1996 04:04:34 -0800 (PST) Received: (from ahill@localhost) by tulpi.interconnect.com.au id XAA26145 (8.6.11/IDA-1.6); Fri, 19 Jan 1996 23:04:19 +1100 Date: Fri, 19 Jan 1996 23:04:17 +1100 (EST) From: Anthony Hill To: questions@freebsd.org Subject: consequences of `bpfilter' pseudo-device Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk All this talk of sniffers and snoopers has made me start playing with tcpdump. I have just built a kernel with 'pseudo-device bpfilter 4', and pseudo-device snp 3'. Tcpdump seems to be working fine. LINT however, carries the rather scary warning :- # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. May I ask, what are the legal and administrative consequences of enabling bpfilter ? Anthony Hill ahill@connect.com.au