Date: Thu, 20 Jan 2000 19:42:43 -0700 From: Brett Glass <brett@lariat.org> To: marcs@go2net.com Cc: freebsd-security@FreeBSD.ORG Subject: Re: bugtraq posts: stream.c - new FreeBSD exploit? Message-ID: <4.2.2.20000120194037.0188de10@localhost> In-Reply-To: <Pine.BSF.4.20.0001201820450.355-100000@alive.znep.com> References: <4.2.2.20000120180821.0188d5c0@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
At 06:23 PM 1/20/2000 , marcs@go2net.com wrote: >On Thu, 20 Jan 2000, Brett Glass wrote: > > > My guess is that there's a long code path, or other inefficiency, > > in the way the ACK is handled. Perhaps a linear search for the > > right socket instead of one that's more clevery implemented > > (e.g. search by port, then address, etc.). > >How about you stop making random guess after random guess about what the >fixes are when you don't even know what the problem is, Actually, I do have some idea about what the problem is. I'm hoping that a quick discussion will lead to (a) a fast workaround to protect many servers -- IPFilter rules would be nice because they could be applied to lots of systems -- and (b) a long-term patch for FreeBSD. I've already been analyzing the worst-case code paths in the kernel. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.2.20000120194037.0188de10>