From owner-freebsd-security  Tue Jul 29 09:26:06 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA26446
          for security-outgoing; Tue, 29 Jul 1997 09:26:06 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26427
          for <security@freebsd.org>; Tue, 29 Jul 1997 09:25:55 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wtF5l-0006nV-00; Tue, 29 Jul 1997 10:25:45 -0600
To: Robert Watson <robert@cyrus.watson.org>
Subject: Re: Detecting sniffers (was: Re: security hole in FreeBSD) 
Cc: security@freebsd.org
In-reply-to: Your message of "Mon, 28 Jul 1997 21:59:39 EDT."
		<Pine.BSF.3.95q.970728215803.4839A-100000@cyrus.watson.org> 
References: <Pine.BSF.3.95q.970728215803.4839A-100000@cyrus.watson.org>  
Date: Tue, 29 Jul 1997 10:25:45 -0600
From: Warner Losh <imp@village.org>
Message-Id: <E0wtF5l-0006nV-00@rover.village.org>
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <Pine.BSF.3.95q.970728215803.4839A-100000@cyrus.watson.org> Robert Watson writes:
: host.  Promiscuous mode simply disables the filter.  The only way to
: prevent the packets from being sniffable is to prevent them from going on
: the wire in question -- smart hubs (switches) do this, so are desirable.

Well, there is strong encryption.  While it doesn't prevent sniff of
the packets, per se, it generally leaves you with garbage and produces
the same net effect.

Warner