From owner-freebsd-stable Sat Jan 5 19:26: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from buffoon.automagic.org (buffoon.automagic.org [208.185.30.208]) by hub.freebsd.org (Postfix) with SMTP id 1002037B41B for ; Sat, 5 Jan 2002 19:26:04 -0800 (PST) Received: (qmail 26349 invoked by uid 1000); 6 Jan 2002 03:26:02 -0000 Date: Sat, 5 Jan 2002 22:26:01 -0500 From: Joe Abley To: cjclark@alum.mit.edu Cc: Haikal Saadh , stable@FreeBSD.ORG Subject: Re: Chrooted bind out of the box Message-ID: <20020105222558.A95067@buffoon.automagic.org> References: <000001c195b1$db087880$41c801ca@warhawk> <20020105140846.D204@gohan.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020105140846.D204@gohan.cjclark.org> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jan 05, 2002 at 02:08:46PM -0800, Crist J. Clark wrote: > On Sat, Jan 05, 2002 at 11:26:00AM +0500, Haikal Saadh wrote: > > Is there a reason why bind is run as root by default and not bind.bind? > > And not chrooted? > > > > If I'm not mistaken almost everyone does this anyway, right? > > IIRC, the last time it was discussed, it was felt changing this in the > middle of -STABLE would be too disruptive. Many working BIND > installations would break when people updated. Why not create a named_chroot variable in defaults/rc.conf which is by default set to NO, but which sysinstall can override in /etc/rc.conf with a YES for fresh (non-upgrade) installs? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message