From owner-freebsd-net@FreeBSD.ORG  Sat Apr 24 07:45:35 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7148916A4D0
	for <net@freebsd.org>; Sat, 24 Apr 2004 07:45:35 -0700 (PDT)
Received: from web80106.mail.yahoo.com (web80106.mail.yahoo.com
	[66.163.169.79])	by mx1.FreeBSD.org (Postfix) with SMTP id 55CC643D31
	for <net@freebsd.org>; Sat, 24 Apr 2004 07:45:35 -0700 (PDT)
	(envelope-from evans.alan@sbcglobal.net)
Message-ID: <20040424144535.81824.qmail@web80106.mail.yahoo.com>
Received: from [66.124.150.213] by web80106.mail.yahoo.com via HTTP;
	Sat, 24 Apr 2004 07:45:35 PDT
Date: Sat, 24 Apr 2004 07:45:35 -0700 (PDT)
From: Alan Evans <evans.alan@sbcglobal.net>
To: net@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: TCP vulnrability
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Apr 2004 14:45:35 -0000

I'm sure FreeBSD is vulnerable.

http://www.us-cert.gov/cas/techalerts/TA04-111A.html

There's a draft that (sort of) addresses this. Should
we
adopt it?

draft-ietf-tcpm-tcpsecure-00.txt

Alan.