From owner-freebsd-security@FreeBSD.ORG  Tue Mar  2 12:59:34 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 57D1416A4CE
	for <freebsd-security@freebsd.org>;
	Tue,  2 Mar 2004 12:59:34 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id B15C243D1F
	for <freebsd-security@freebsd.org>;
	Tue,  2 Mar 2004 12:59:33 -0800 (PST)	(envelope-from silby@silby.com)
Received: (qmail 71070 invoked from network); 2 Mar 2004 20:59:32 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 2 Mar 2004 20:59:32 -0000
X-pair-Authenticated: 209.68.2.70
Date: Tue, 2 Mar 2004 14:59:25 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Darren Reed <avalon@caligula.anu.edu.au>
In-Reply-To: <200403021808.i22I87XN007054@caligula.anu.edu.au>
Message-ID: <20040302145808.R715@odysseus.silby.com>
References: <200403021808.i22I87XN007054@caligula.anu.edu.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-security@freebsd.org
Subject: Re: mbuf vulnerability
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, 02 Mar 2004 20:59:34 -0000


On Wed, 3 Mar 2004, Darren Reed wrote:

> > > "strict" requires that the sequence number in packet n should match
> > > what that sequence number of the last byte in packet n-1 - i.e. no
> > > out of order delivery is permitted.
> > >
> > > Darren
> Right, so your comment about it "not working" applies to 3.x (which
> is what comes with freebsd, currently), which is what i was hoping :)
>
> My comment was to say that with ipf4, you can address this problem.
>
> darren

Ok, that sounds correct.  However, it would have an adverse performance
impact in the normal case.  Have you considered having an "almost strict"
option that would allow maybe 3 or 4 out of order segments through?  That
would be a great feature. :)

Mike "Silby" Silbersack