From owner-freebsd-security@FreeBSD.ORG Sat Jul 12 05:20:55 2008 Return-Path: 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 A054C106564A; Sat, 12 Jul 2008 05:20:55 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 0CF558FC14; Sat, 12 Jul 2008 05:20:52 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id OAA05486; Sat, 12 Jul 2008 14:49:18 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 12 Jul 2008 14:49:17 +1000 (EST) From: Ian Smith To: Mark Andrews In-Reply-To: <200807112219.m6BMJmLg042450@drugs.dv.isc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Doug Barton , stef@memberwebs.com, "freebsd-security@freebsd.org" , secteam@freebsd.org, Brett Glass , Remko Lodder , Andrew Storms Subject: Re: [Fwd: cvs commit: ports/dns/bind9 Makefile distinfo ports/dns/bind94 Makefile distinfo ports/dns/bind95 Makefile distinfo] 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: Sat, 12 Jul 2008 05:20:55 -0000 On Sat, 12 Jul 2008, Mark Andrews wrote: > > > Is there a way to restrict the ports which BIND selects -- perhaps > > at the expense of a small amount of entropy -- such that it doesn't > > try to use UDP ports which are administratively blocked (e.g. ports > > used by worms, or insecure Microsoft network utilities)? We don't > > dare turn these port blocks off, or naive users will fall prey to > > security holes in Microsoft products. But if BIND doesn't know to > > work around them, lookups will occasionally (and infuriatingly!) > > fail. > > % grep avoid doc/misc/options > avoid-v4-udp-ports { ; ... }; > avoid-v6-udp-ports { ; ... }; > % This seems to imply that you can't specify ranges of UDP ports to avoid here. For example perhaps, the range traceroute uses .. Doug responded with a new option for a range of ports to use, but an intersection of ports to use and ^ports to avoid, including range(s), would cover all the bases .. cheers, Ian