From owner-freebsd-security Fri Jan 21 15:54: 7 2000 Delivered-To: freebsd-security@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3DEE7158F2 for ; Fri, 21 Jan 2000 15:53:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA64927; Fri, 21 Jan 2000 15:53:28 -0800 (PST) (envelope-from dillon) Date: Fri, 21 Jan 2000 15:53:28 -0800 (PST) From: Matthew Dillon Message-Id: <200001212353.PAA64927@apollo.backplane.com> To: Poul-Henning Kamp Cc: Alfred Perlstein , Brett Glass , security@FreeBSD.ORG Subject: Re: stream.c worst-case kernel paths References: <7263.948497709@critter.freebsd.dk> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :> It may be worth doing this sort of patch after the release, but if the goal :> of the release is to fix bugs then the proper solution is to use the one that :> we know already makes a difference - restricting the output path. : :And you conveniently forgot to quote the one line of my email where I :said as much. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." Sorry about that. I'm freaking out a little because we are too damn close to release to be making any big changes to the network stack and protocols. Frankly, big changes are not necessary. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message