From owner-freebsd-security@FreeBSD.ORG  Mon Jul 17 18:59:20 2006
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 9230216A4DE;
	Mon, 17 Jul 2006 18:59:20 +0000 (UTC)
	(envelope-from ari@suutari.iki.fi)
Received: from pne-smtpout3-sn1.fre.skanova.net
	(pne-smtpout3-sn1.fre.skanova.net [81.228.11.120])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1BBB343D45;
	Mon, 17 Jul 2006 18:59:19 +0000 (GMT)
	(envelope-from ari@suutari.iki.fi)
Received: from mato.suutari.iki.fi (80.222.160.17) by
	pne-smtpout3-sn1.fre.skanova.net (7.2.075)
	id 44A13099000A05B7; Mon, 17 Jul 2006 20:59:18 +0200
Received: from [127.0.0.1] (raisa.suutari.iki.fi [192.168.60.100])
	by mato.suutari.iki.fi (8.13.6/8.13.6) with ESMTP id k6HIxGJs012613;
	Mon, 17 Jul 2006 21:59:16 +0300 (EEST)
	(envelope-from ari@suutari.iki.fi)
Message-ID: <44BBDE0B.6050004@suutari.iki.fi>
Date: Mon, 17 Jul 2006 21:59:23 +0300
From: Ari Suutari <ari@suutari.iki.fi>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Simon L. Nielsen" <simon@nitro.dk>
References: <44B7715E.8050906@suutari.iki.fi>
	<20060714154729.GA8616@psconsult.nl>
	<44B7D8B8.3090403@suutari.iki.fi>
	<20060716182315.GC3240@insomnia.benzedrine.cx>
	<20060717122127.GC1087@zaphod.nitro.dk>
In-Reply-To: <20060717122127.GC1087@zaphod.nitro.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 0628-5, 14.07.2006), Outbound message
X-Antivirus-Status: Clean
Cc: freebsd-security@freebsd.org, freebsd-pf@freebsd.org
Subject: Re: Any ongoing effort to port /etc/rc.d/pf_boot, /etc/pf.boot.conf
 from NetBSD ?
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: Mon, 17 Jul 2006 18:59:20 -0000

Hi,
Simon L. Nielsen wrote:
> Since nobody else seems to have actually done this, I took a look at
> FreeBSD's rcorder (on my -CURRENT laptop) and actually I don't really
> see a hole.  Most importantly pf is enabled before routing.

	I did this yesterday, but this thread has gotten quite active
	so maybe you lost the results. But my findings were same as
	yours: pf is enabled before routing which means that the 	
	hole I was afraid of doesn't exist.
> 
> Personally I would still like a default to deny knob, but that's
> mainly to handle the case of an invalid ruleset which causes pf to be
> left open.  Yes, this is only a problem when the admin screws up, but
> it happens...

	Yes, and it might be quite common: some edits ruleset but
	leaves it unfinished because other, more high-priority
	jobs arrive (from boss...) and the someone other accidentally
	reboots your firewall... Default deny (or rc.d/pf_boot) would
	help here.

		Ari S.