Date: Fri, 21 Jan 2000 16:25:42 -0700 From: Warner Losh <imp@village.org> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Darren Reed <avalon@coombs.anu.edu.au>, brett@lariat.org (Brett Glass), security@FreeBSD.ORG Subject: Re: stream.c worst-case kernel paths Message-ID: <200001212325.QAA15279@harmony.village.org> In-Reply-To: Your message of "Fri, 21 Jan 2000 15:21:25 PST." <200001212321.PAA64674@apollo.backplane.com> References: <200001212321.PAA64674@apollo.backplane.com> <200001210417.PAA24853@cairo.anu.edu.au> <200001210642.XAA09108@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200001212321.PAA64674@apollo.backplane.com> Matthew Dillon writes: : Either way this is not a big deal. Lobotomizing TCP is not necessary. I'm starting to agree with this. There have been lots of reports of ICMP_LIMIT working well. If we make changes in this area, then I'm leaning toward Matt's path. I would be *EXTREMELY* reluctant to do anything to change the tcp state machine that isn't triggered by the same mechanism used by ICMP_LIMIT. I certainly wouldn't want to break our stack by default. Warner 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?200001212325.QAA15279>