From owner-freebsd-security Fri Jan 21 7:54:17 2000 Delivered-To: freebsd-security@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 7532A15113 for ; Fri, 21 Jan 2000 07:54:07 -0800 (PST) (envelope-from trouble@netquick.net) Received: from bastille.netquick.net ([216.48.32.159] ident=root) by bekool.com with smtp (Exim 3.03 #1) id 12BgwC-0002vn-00; Fri, 21 Jan 2000 11:29:28 -0500 From: TrouBle Date: Fri, 21 Jan 2000 16:08:24 GMT Message-ID: <20000121.16082400@bastille.netquick.net> Subject: Re: stream.c worst-case kernel paths To: Darren Reed Cc: oogali@intranova.net (Omachonu Ogali), brett@lariat.org (Brett Glass), security@FreeBSD.ORG In-Reply-To: <200001211415.BAA12772@cairo.anu.edu.au> References: <200001211415.BAA12772@cairo.anu.edu.au> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.1; Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org So can i get a straight answer, is there yet a patch to fix this=20 problem under current ?? does it affect current ??? and 3.3 and 3.4 ????? if so where can i get it cause i have 5 public=20 boxes, and we gots enemies.... these boxes run 3.2, 3.3 3.4 and 4.0 also is there a way to test the vulnerability is gone after patching=20 ??? guess ill upgrade them all to 3.4 but i need to patch them before=20 some idiot takes em down in a cloud of packets To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message