From owner-freebsd-security Fri Jan 21 14:27:10 2000 Delivered-To: freebsd-security@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5C91A154D3 for ; Fri, 21 Jan 2000 14:27:05 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA20392; Fri, 21 Jan 2000 14:26:25 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA08318; Fri, 21 Jan 2000 14:26:24 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA03680; Fri, 21 Jan 2000 14:25:03 -0800 (PST) Message-ID: <3888DE17.9FC77026@softweyr.com> Date: Fri, 21 Jan 2000 15:30:47 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Brett Glass Cc: security@freebsd.org Subject: Re: stream.c worst-case kernel paths References: <200001211415.BAA12772@cairo.anu.edu.au> <20000121.16082400@bastille.netquick.net> <4.2.2.20000121140941.01a68b30@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brett Glass wrote: > > At 01:55 PM 1/21/2000 , Wes Peters wrote: > > >Be warned if you're using the exploit program: if you select random > >addresses, it may (will) pick multicast IP addresses, which may have > >unintended side affects on your network. Augh! > > Geeze. Is it even LEGAL to ACK multicast packets? It certainly isn't legal to have multicast TCP... This is going to drive the Layer 3 switch vendors crazy. ;^( -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message