From owner-freebsd-security@FreeBSD.ORG Fri Jul 11 05:05:38 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 82F121065670 for ; Fri, 11 Jul 2008 05:05:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 126C18FC1E for ; Fri, 11 Jul 2008 05:05:37 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 12839 invoked by uid 399); 11 Jul 2008 05:05:37 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 11 Jul 2008 05:05:37 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4876EA1E.9000804@FreeBSD.org> Date: Thu, 10 Jul 2008 22:05:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: stef@memberwebs.com References: <20080709204114.471A2F1835D@mx.npubs.com> <4876A3FE.1070407@FreeBSD.org> In-Reply-To: <4876A3FE.1070407@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-security@freebsd.org" , Remko Lodder , secteam@freebsd.org, 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: Fri, 11 Jul 2008 05:05:38 -0000 Doug Barton wrote: > However, named is still picking a "random" UDP port on startup and > locking it down (2 if you're also using IPv6) although it's not > immediately clear to me why. And the answer is .... in order to make the -P1 releases as clean as possible, that part of the code was not touched (which I think is a very good decision) and that port may continue to see use down the road. hope this helps, Doug -- This .signature sanitized for your protection