From owner-freebsd-security@FreeBSD.ORG Wed Jul 6 03:56:56 2005 Return-Path: X-Original-To: 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 5BCEA16A41C for ; Wed, 6 Jul 2005 03:56:56 +0000 (GMT) (envelope-from avalon@caligula.anu.edu.au) Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDF2A43D48 for ; Wed, 6 Jul 2005 03:56:55 +0000 (GMT) (envelope-from avalon@caligula.anu.edu.au) Received: from caligula.anu.edu.au (localhost [127.0.0.1]) by caligula.anu.edu.au (8.12.9/8.12.9) with ESMTP id j663ueOw011745; Wed, 6 Jul 2005 13:56:40 +1000 (EST) Received: (from avalon@localhost) by caligula.anu.edu.au (8.12.9/8.12.8/Submit) id j663ucHE011742; Wed, 6 Jul 2005 13:56:38 +1000 (EST) From: Darren Reed Message-Id: <200507060356.j663ucHE011742@caligula.anu.edu.au> To: rcoleman@criticalmagic.com (Richard Coleman) Date: Wed, 6 Jul 2005 13:56:38 +1000 (Australia/ACT) In-Reply-To: <42CAA33D.9080505@criticalmagic.com> from "Richard Coleman" at Jul 05, 2005 11:11:57 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-security@freebsd.org, Garrett Wollman , Jesper Wallin , Darren Reed , =?ISO-8859-1?Q?Dag-Erling_?= =?ISO-8859-1?Q?Sm=F8rgrav?= Subject: Re: packets with syn/fin vs pf_norm.c X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2005 03:56:56 -0000 In some mail from Richard Coleman, sie said: > 1. I thought that T/TCP was being removed from FreeBSD (already happened?). > 2. It's trivial to predict Theo's response to this. > 3. Since T/TCP is rare, there is little motivation to alter scrub to > function differently than OpenBSD with respect to these packets. If > someone really needs this, there are plenty of alternatives. I didn't know about (1) but I'd agree with (2) and (3). > But more importantly, the original question has been lost. The original > question was what should the various firewalls do when the kernel has > been compiled with TCP_DROP_SYNFIN. Regardless of whether those packets > are valid or not, a person may have reason to compile this feature into > the kernel. So, should the firewalls acts differently if this kernel > option is used? IMHO, No. Darren