From owner-freebsd-questions@FreeBSD.ORG Mon Feb 9 19:20:44 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 12D6ACC5 for ; Mon, 9 Feb 2015 19:20:44 +0000 (UTC) Received: from a0i241.smtpcorp.com (a0i241.smtpcorp.com [216.22.15.73]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DE4E1DE for ; Mon, 9 Feb 2015 19:20:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a0_1; h=Feedback-ID:X-Smtpcorp-Track:Message-ID:Date:Subject:To:From; bh=KqBAjyrwWybp1llaq+WMMnckJhTbsp168dDxsybhpg0=; b=ewXSqUWpxHqDZRUMwTgUYuRSOnpf6gLeQ/nM9+whc6sHzJkhLvTNjpDvoReD2FlpxHPAqyBa1buma6GmLLhZjZl27OWDJ2E1NMJi+jod4KDWzf64oDXbltGoJvC1YlM8GXWgUZGHQP1L+2+lADaI+vOsx/sEBvjSs+xhiN9LISg=; From: Daniel Corbe To: Lowell Gilbert Subject: Re: /etc/pf.conf missing References: <44h9uvvwkd.fsf@lowell-desk.lan> Date: Mon, 09 Feb 2015 14:20:43 -0500 In-Reply-To: <44h9uvvwkd.fsf@lowell-desk.lan> (Lowell Gilbert's message of "Mon, 09 Feb 2015 12:12:02 -0500") Message-ID: <87twyuj3hw.fsf@corbe.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Smtpcorp-Track: 1YKtswmk-zWw7M.2QiLF3dvq Feedback-ID: 10661m:10661aegzayD:10661sqsQoeqcWA:SMTPCORP Cc: freebsd-questions , Chris Stankevitz X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 19:20:44 -0000 Lowell Gilbert writes: > Chris Stankevitz writes: > >> Q: Should I be alarmed? >> >> Handbook section 30.3.1 says "The default ruleset is already created >> and is named /etc/pf.conf" but that file does not exist on my hard >> drive. > > The Handbook (or at least the obvious interpretation of what it says; > the awkward phrasing may mean that it was mis-edited at some point) is > incorrect. > > I'm not sure that a one-size-fits-all default ruleset (of the sort that > exists for ipfw) is practical for pf. > > The first time I ever messed with pf it was extremely difficult finding practical examples. Maybe what the distribution needs is more of this and less of a one-size-fits-all approach. Teaching tools in the form of configuration examples is also a great way to get people thinking about security issues. For example: How do you get small offices and home users thinking about inbound connectivity to their IPv6 endpoints now that NAT is no longer a thing? And I know NAT is a terrible example of a security model; but generally speaking, people are going to want NAT-like functionality in IPv6 where you're only passing inbound traffic to inside hosts on established connections. IE: # Default deny block out inet6 all block in inet6 all # NAT-like behavior pass out inet6 proto tcp flags S/SA keep state pass out inet6 proto {udp, icmp6} flags S/SA modulate state # Inbound rules go here ...