From owner-freebsd-current Fri Mar 31 0:29:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 6F50237B994 for ; Fri, 31 Mar 2000 00:29:33 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id A7CEE1E00A; Fri, 31 Mar 2000 03:29:13 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id DAA01584; Fri, 31 Mar 2000 03:29:12 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id AAA02707; Fri, 31 Mar 2000 00:28:22 -0800 (PST) Message-Id: <200003310828.AAA02707@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jkh@zippy.cdrom.com Subject: Re: So, AGAIN, why was tcpdump moved? Cc: current@freebsd.org Date: Fri, 31 Mar 2000 00:28:22 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just out of curiosity, why is there an "AGAIN" in the subject line, since this is the first email I've gotten on the subject? tcpdump is capable of decrypting ESP, if you give it the key and if it's linked with libcrypto. Since IPSEC is part of FreeBSD, and libcrypto is part of FreeBSD, I figured it would be a nice thing to have. It didn't occur to me that this would change where tcpdump lived (i.e. it seemed like libcrypto was part of FreeBSD) so it wasn't an explicit choice on my part to move distributions. I agree that's a bad side effect. It's easy to disable the decrypting-ESP feature if the disadvantage of having it is greater than the advantage. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message