Date: Sat, 22 Jan 2000 00:35:09 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Alfred Perlstein <bright@wintelcom.net>, Brett Glass <brett@lariat.org>, security@FreeBSD.ORG Subject: Re: stream.c worst-case kernel paths Message-ID: <7263.948497709@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 21 Jan 2000 15:31:10 PST." <200001212331.PAA64734@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200001212331.PAA64734@apollo.backplane.com>, Matthew Dillon writes: > Except that this will not fix anything. You are saving yourself a small > amount of cpu -- not enough to matter, really, in an attack of this sort. > 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." FreeBSD -- It will take a long time before progress goes too far! 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?7263.948497709>