Date: Tue, 20 Apr 2004 19:40:23 -0400 From: Mike Tancsa <mike@sentex.net> To: "Crist J. Clark" <cjc@freebsd.org>, freebsd-security@freebsd.org Subject: Re: TCP RST attack Message-ID: <6.0.3.0.0.20040420193554.07da5780@209.112.4.2> In-Reply-To: <20040420202422.GB3727@blossom.cjclark.org> 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
At 04:24 PM 20/04/2004, Crist J. Clark wrote: >Arguments on the severity of the bug aside, FreeBSD does not >have a working RFC2385 implementation. Most of it is there http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netipsec/ipsec.h has info about it. bms@freebsd.org is also working on completing the rest. I have been using his patches against quagga on a directly connected ebgp peer as well as an ebgp multi-hop peer as well for a good 2 months and it works as expected. ---Mike >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 >already have patches? >-- >Crist J. Clark | cjclark@alum.mit.edu > | cjclark@jhu.edu >http://people.freebsd.org/~cjc/ | cjc@freebsd.org >_______________________________________________ >freebsd-security@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-security >To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.3.0.0.20040420193554.07da5780>