From owner-freebsd-security@FreeBSD.ORG  Fri May  2 09:50:14 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CE3D7B06
 for <freebsd-security@freebsd.org>; Fri,  2 May 2014 09:50:14 +0000 (UTC)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 927A9126A
 for <freebsd-security@freebsd.org>; Fri,  2 May 2014 09:50:14 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id D3C8D61B5;
 Fri,  2 May 2014 09:50:13 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id 60EF231A33; Fri,  2 May 2014 11:50:16 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Mike Tancsa <mike@sentex.net>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:08.tcp
References: <201404300435.s3U4ZAw1093717@freefall.freebsd.org>
 <53610127.5000603@sentex.net>
Date: Fri, 02 May 2014 11:50:16 +0200
In-Reply-To: <53610127.5000603@sentex.net> (Mike Tancsa's message of "Wed, 30
 Apr 2014 09:56:55 -0400")
Message-ID: <86y4ykik6f.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-security@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Fri, 02 May 2014 09:50:14 -0000

Mike Tancsa <mike@sentex.net> writes:
> Is [scrub in all] the only pf option that will work, or is scrub
> fragment reassemble sufficient ?

"fragment reassemble" is implicit, but if you leave out "in" it will
also scrub outgoing traffic, which is wasteful.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no