From owner-freebsd-security Sat Dec 18 11:13:17 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 0945B14D4B for ; Sat, 18 Dec 1999 11:13:15 -0800 (PST) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id MAA12115; Sat, 18 Dec 1999 12:13:03 -0700 (MST) Message-Id: <4.2.0.58.19991218120838.00cebcd0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 18 Dec 1999 12:09:18 -0700 To: Bosko Milekic , jason schwab From: Brett Glass Subject: Re: !!!really, really big problem with *BSD!!! Cc: freebsd-security@FreeBSD.ORG In-Reply-To: References: <19991217060946.67059.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:28 PM 12/16/1999 , Bosko Milekic wrote: > This situation has been fixed, in two different ways which, for what > concerns this particular "problem" (really, it's a resource exhaustion) > in -CURRENT: > > (a) Limit sockbuf size. > > (b) Code has been added to -CURRENT which will prevent the system > from going down. (e.g. panic()). Will there also be a fix in 3.4? --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message