From owner-freebsd-security Thu Jan 20 17:24:24 2000 Delivered-To: freebsd-security@freebsd.org Received: from alive.znep.com (alive.znep.com [207.167.15.58]) by hub.freebsd.org (Postfix) with ESMTP id DB82A153E6 for ; Thu, 20 Jan 2000 17:24:12 -0800 (PST) (envelope-from marcs@go2net.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.3/8.9.1) with ESMTP id SAA80912; Thu, 20 Jan 2000 18:23:34 -0700 (MST) (envelope-from marcs@go2net.com) From: marcs@go2net.com X-Authentication-Warning: alive.znep.com: marcs owned process doing -bs Date: Thu, 20 Jan 2000 18:23:34 -0700 (MST) X-Sender: marcs@alive.znep.com To: Brett Glass Cc: freebsd-security@FreeBSD.ORG Subject: Re: bugtraq posts: stream.c - new FreeBSD exploit? In-Reply-To: <4.2.2.20000120180821.0188d5c0@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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, and leave it to someone who knows the details of exactly what it does and what impact it has? Seems like every two minutes you send a new message to the list with a new guess at what could fix it. No useful purpose is served by flooding mailing lists with speculation after speculation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message