From owner-freebsd-security@FreeBSD.ORG  Tue Apr 20 14:20:48 2004
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5699F16A4CE; Tue, 20 Apr 2004 14:20:48 -0700 (PDT)
Received: from smtp.des.no (flood.des.no [217.116.83.31])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AD6AE43D1F; Tue, 20 Apr 2004 14:20:47 -0700 (PDT)
	(envelope-from des@des.no)
Received: by smtp.des.no (Pony Express, from userid 666)
	id 6AF6E5311; Tue, 20 Apr 2004 23:20:46 +0200 (CEST)
Received: from dwp.des.no (des.no [80.203.228.37])
	by smtp.des.no (Pony Express) with ESMTP
	id 84C6D530A; Tue, 20 Apr 2004 23:20:39 +0200 (CEST)
Received: by dwp.des.no (Postfix, from userid 2602)
	id 2B09633C6C; Tue, 20 Apr 2004 23:20:39 +0200 (CEST)
To: "Crist J. Clark" <cjc@freebsd.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>
From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=)
Date: Tue, 20 Apr 2004 23:20:39 +0200
In-Reply-To: <20040420202422.GB3727@blossom.cjclark.org> (Crist J. Clark's
 message of "Tue, 20 Apr 2004 13:24:22 -0700")
Message-ID: <xzp3c6yibx4.fsf@dwp.des.no>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no
X-Spam-Level: 
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63
cc: freebsd-security@freebsd.org
Subject: Re: TCP RST attack
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2004 21:20:48 -0000

"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