From owner-freebsd-security@FreeBSD.ORG  Sat May  3 05:25:43 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D561D99D
 for <freebsd-security@freebsd.org>; Sat,  3 May 2014 05:25:43 +0000 (UTC)
Received: from hergotha.csail.mit.edu
 (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8E9AB156D
 for <freebsd-security@freebsd.org>; Sat,  3 May 2014 05:25:43 +0000 (UTC)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
 by hergotha.csail.mit.edu (8.14.7/8.14.7) with ESMTP id s435Pe38026964;
 Sat, 3 May 2014 01:25:40 -0400 (EDT)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
 by hergotha.csail.mit.edu (8.14.7/8.14.4/Submit) id s435Pe6g026961;
 Sat, 3 May 2014 01:25:40 -0400 (EDT) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21348.32212.390793.959943@hergotha.csail.mit.edu>
Date: Sat, 3 May 2014 01:25:40 -0400
From: Garrett Wollman <wollman@bimajority.org>
To: Ian Smith <smithi@nimnet.asn.au>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:08.tcp
In-Reply-To: <20140503133437.R11699@sola.nimnet.asn.au>
References: <3867.1399059743@server1.tristatelogic.com>
 <5363FA70.9040100@delphij.net>
 <20140503133437.R11699@sola.nimnet.asn.au>
X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (hergotha.csail.mit.edu [127.0.0.1]); Sat, 03 May 2014 01:25:40 -0400 (EDT)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,
 HEADER_FROM_DIFFERENT_DOMAINS autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
 hergotha.csail.mit.edu
X-Mailman-Approved-At: Sat, 03 May 2014 12:25:48 +0000
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: Sat, 03 May 2014 05:25:43 -0000

<<On Sat, 3 May 2014 13:53:44 +1000 (EST), Ian Smith <smithi@nimnet.asn.au> said:

> I've always allowed frags, as per the example rulesets in rc.firewall.  
> I only recall seeing them on DNS responses from zen.spamhaus.org, where 
> I see plenty of these after a resetlog before the logging limit kicks 
> in.  I doubt I'd be getting rid of ~90% of incoming spam without; eg:

Blocking inbound fragments will definitely screw you when you try to
use DNSsec.

-GAWollman