Date: Sun, 24 Feb 2002 10:27:46 -0800 From: "Crist J. Clark" <crist.clark@attbi.com> To: Ruslan Ermilov <ru@FreeBSD.ORG> Cc: Maxim Konovalov <maxim@macomnet.ru>, net@FreeBSD.ORG, Robert Watson <rwatson@FreeBSD.ORG> Subject: Re: TCP Connections to a Broadcast Address Message-ID: <20020224102746.Q16048@blossom.cjclark.org> In-Reply-To: <20020224084921.GC31243@sunbay.com>; from ru@FreeBSD.ORG on Sun, Feb 24, 2002 at 10:49:21AM %2B0200 References: <20020223042828.E16048@blossom.cjclark.org> <20020223154842.G31228-100000@news1.macomnet.ru> <20020224084921.GC31243@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 24, 2002 at 10:49:21AM +0200, Ruslan Ermilov wrote:
> On Sat, Feb 23, 2002 at 03:49:55PM +0300, Maxim Konovalov wrote:
> > On 04:28-0800, Feb 23, 2002, Crist J. Clark wrote:
> >
> > > On Sat, Feb 23, 2002 at 01:50:33PM +0200, Ruslan Ermilov wrote:
> > > [snip]
> > >
> > > > Nice catch!
> > >
> > > Igor M Podlesny <poige@morning.ru>, PR misc/35022, caught it. I just
> > > analyzed it.
> >
> > Isn't kern/19722 about the same bug?
> >
> Yes.
I think there are some different issues raised in this PR too. Like
the discussion in another part of this thread, PR 19722 states that
you can reach the broadcast address of interfaces other than the one
to which the attacker is directly attached. I have not been able to
reproduce this. I think it was fixed by revision 1.181 of ip_input.c.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020224102746.Q16048>