Date: Tue, 20 Apr 2004 23:20:39 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: "Crist J. Clark" <cjc@freebsd.org> Cc: freebsd-security@freebsd.org Subject: Re: TCP RST attack Message-ID: <xzp3c6yibx4.fsf@dwp.des.no> In-Reply-To: <20040420202422.GB3727@blossom.cjclark.org> (Crist J. Clark's message of "Tue, 20 Apr 2004 13:24:22 -0700") References: <6.0.3.0.0.20040420125557.06b10d48@209.112.4.2> <xzphdve35oa.fsf@dwp.des.no> <200404201113.27737.dr@kyx.net> <xzp65buh5fa.fsf@dwp.des.no> <6.0.3.0.0.20040420144001.0723ab80@209.112.4.2> <20040420202422.GB3727@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Crist J. Clark" <cristjc@comcast.net> writes: > Arguments on the severity of the bug aside, FreeBSD does not > have a working RFC2385 implementation. And despite any particular > FreeBSD developer's opinion of the severity, there will be some > FreeBSD consumers who want RFC2385. Anyone working on it or=20 > already have patches? We already have a partial implementation in the tree, and work is ongoing to complete it. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp3c6yibx4.fsf>