From owner-freebsd-security@FreeBSD.ORG  Tue Apr 20 13:24:28 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 60F9916A4CF
	for <freebsd-security@freebsd.org>;
	Tue, 20 Apr 2004 13:24:28 -0700 (PDT)
Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3748843D60
	for <freebsd-security@freebsd.org>;
	Tue, 20 Apr 2004 13:24:28 -0700 (PDT)
	(envelope-from cristjc@comcast.net)
Received: from blossom.cjclark.org
	(c-24-6-187-112.client.comcast.net[24.6.187.112])
	by comcast.net (rwcrmhc12) with ESMTP
	id <2004042020242701400rlu17e>; Tue, 20 Apr 2004 20:24:27 +0000
Received: from blossom.cjclark.org (localhost. [127.0.0.1])
	by blossom.cjclark.org (8.12.9p2/8.12.8) with ESMTP id i3KKON8B004407
	for <freebsd-security@freebsd.org>;
	Tue, 20 Apr 2004 13:24:27 -0700 (PDT)
	(envelope-from cristjc@comcast.net)
Received: (from cjc@localhost)
	by blossom.cjclark.org (8.12.9p2/8.12.9/Submit) id i3KKOM7T004406
	for freebsd-security@freebsd.org;
	Tue, 20 Apr 2004 13:24:23 -0700 (PDT)
	(envelope-from cristjc@comcast.net)
X-Authentication-Warning: blossom.cjclark.org: cjc set sender to
	cristjc@comcast.net using -f
Date: Tue, 20 Apr 2004 13:24:22 -0700
From: "Crist J. Clark" <cristjc@comcast.net>
To: freebsd-security@freebsd.org
Message-ID: <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.0.3.0.0.20040420144001.0723ab80@209.112.4.2>
User-Agent: Mutt/1.4.2.1i
X-URL: http://people.freebsd.org/~cjc/
Subject: Re: TCP RST attack
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: "Crist J. Clark" <cjc@freebsd.org>
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 20:24:28 -0000

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 
already have patches?
-- 
Crist J. Clark                     |     cjclark@alum.mit.edu
                                   |     cjclark@jhu.edu
http://people.freebsd.org/~cjc/    |     cjc@freebsd.org