From owner-freebsd-security  Sat Nov 22 22:41:04 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA22782
          for security-outgoing; Sat, 22 Nov 1997 22:41:04 -0800 (PST)
          (envelope-from owner-freebsd-security)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA22772
          for <security@freebsd.org>; Sat, 22 Nov 1997 22:41:02 -0800 (PST)
          (envelope-from jas@flyingfox.com)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id WAA09478;
	Sat, 22 Nov 1997 22:42:01 -0800 (PST)
Date: Sat, 22 Nov 1997 22:42:01 -0800 (PST)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199711230642.WAA09478@biggusdiskus.flyingfox.com>
To: security@freebsd.org
Subject: Re: LAND attack update
Cc: mycroft@MIT.EDU
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

mycroft@mit.edu (Charles M. Hannum) allegedly wrote:

> The FreeBSD hack to `fix' (or not allow) self-connects DOES NOT WORK
> FOR MULTIHOMED HOSTS.  It's still possible to crash a multihomed
> FreeBSD system by locally running a program that connects a TCP socket
> to itself.

Really?  Show me.

Jim Shankland
Flying Fox Computer Systems, Inc.