From owner-freebsd-security@FreeBSD.ORG  Tue Jul 29 14:38:16 2008
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C596E1065679
	for <freebsd-security@freebsd.org>;
	Tue, 29 Jul 2008 14:38:16 +0000 (UTC)
	(envelope-from jeff+freebsd@wagsky.com)
Received: from mail.wagsky.com (wildside.wagsky.com [64.220.148.97])
	by mx1.freebsd.org (Postfix) with ESMTP id A74E88FC15
	for <freebsd-security@freebsd.org>;
	Tue, 29 Jul 2008 14:38:16 +0000 (UTC)
	(envelope-from jeff+freebsd@wagsky.com)
Received: from port5.pn.wagsky.com (port5.pn.wagsky.com [192.168.6.5])
	by mail.wagsky.com (Postfix) with ESMTPSA id DF6982844A;
	Tue, 29 Jul 2008 07:38:15 -0700 (PDT)
Message-ID: <488F2B57.7000706@wagsky.com>
Date: Tue, 29 Jul 2008 07:38:15 -0700
From: Jeff Kletsky <jeff+freebsd@wagsky.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ipfw "bug" - recv any = not recv any
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
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, 29 Jul 2008 14:38:16 -0000

> In practice, both "recv any" and "not recv any" appear to be "no-op" 
> phrases.
> 
[...]
> In my opinion, the following would be "ideal"
> 
> 1) "recv any" -- matches packets that have been received by the host 
> through one of its interfaces
> 2) "not recv any" -- does not match packets that have been received by 
> the host through one of its interfaces
> 
> Unfortunately, implementing (1) would likely break a lot of people's 
> rule sets
> 
> (2), however, I can't immediately see being used without expecting that 
> it would fail to match packets that were received by the current host, 
> so its implementation would be a bit "safer" for the community
> 

Julian Elishcher suggested:

> how does "not recv *" (appropriatly escaped for your shell) do?


This does appear to "work as desired" -- suggesting documentation clarification rather than functionality change

My apologies for not posting to the ipfw list.


Jeff