From owner-freebsd-stable@FreeBSD.ORG Tue Dec 3 17:30:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25608E18; Tue, 3 Dec 2013 17:30:35 +0000 (UTC) Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E76E3138C; Tue, 3 Dec 2013 17:30:34 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id jt11so21609974pbb.28 for ; Tue, 03 Dec 2013 09:30:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3sY0jzF10w81rvWeuxZEM1QMR8UycOg6GpKDeDwiij8=; b=ccDMyRJZqytXOlWtvwCvlkiDlCwPtzT87E3+ns9YNqolBvezQcCFdAk63ZVB6y6xbO el/ScdPd6zA2WFYEnHrK7X5PEW95FuUj+UkUZu18OBPOld6x9F4QnYkUyKJ5OOdRaamV up/HZo+e2Bk9h/CIiNwUE/zPVSCxGzgUMnln+LwCLMx+lUmq72sFOYJ/acWMvluGQEjk bM3M7oIv4fjuQg5ofgV6mEQzbPylzyQ41u6ZdU1wDq4VXkOh1y8PZ4mSJTG0gYcgmjjn bxttgcJ6udTgE4av6P254ekUDfHRDIwnjekxsnsDOC08OL6b0HxZFy+ry//mI35VnJqO S3Ow== MIME-Version: 1.0 X-Received: by 10.68.185.68 with SMTP id fa4mr40348042pbc.136.1386091832892; Tue, 03 Dec 2013 09:30:32 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Tue, 3 Dec 2013 09:30:32 -0800 (PST) In-Reply-To: <1386086749.9599.54995173.6CD35E54@webmail.messagingengine.com> References: <529D9CC5.8060709@rancid.berkeley.edu> <529DF7FA.7050207@passap.ru> <1386086749.9599.54995173.6CD35E54@webmail.messagingengine.com> Date: Tue, 3 Dec 2013 09:30:32 -0800 X-Google-Sender-Auth: 3VAzPOLt_-8_D-4_28XFtkdP3Ho Message-ID: Subject: Re: BIND chroot environment in 10-RELEASE...gone? From: Kevin Oberman To: Mark Felder Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-stable@freebsd.org Stable" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 17:30:35 -0000 On Tue, Dec 3, 2013 at 8:05 AM, Mark Felder wrote: > On Tue, Dec 3, 2013, at 9:58, Royce Williams wrote: > > On Tue, Dec 3, 2013 at 6:25 AM, Boris Samorodov wrote: > > > > > > 03.12.2013 12:56, Michael Sinatra =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > > > > > I am aware of the fact that unbound has "replaced" BIND in the base > > > > system, starting with 10.0-RELEASE. What surprised me was recent > > > > commits to ports/dns/bind99 (and presumably other versions) that > appears > > > > to take away the supported chroot capabilities. > > > > > > /usr/ports/UPDATING has some info about the matter. > > > > > > Specifically, 20131112 says: > > > > All bind9 ports have been updated to support FreeBSD 10.x after > > BIND was removed from the base system. It is now self-contained > > in ${PREFIX}/etc/namedb, and chroot and symlinking options are > > no longer supported out of the box. > > > > Does that mean that those options now need to be manually configured > > by each team running BIND? > > > > If so, that is a net negative for security. Even if everyone running > > public-facing BIND knows how to chroot, it means more work -- and more > > potential implementation errors. > > > > I had not seen that UPDATING entry... I assume that due to shortage of > time by the maintainer and the urgency to just get the port working it > has been discarded for now. You could try adding the features back to > the port and seeing if the maintainer accepts them. Unfortunately I > don't have any inside information to assist you further. > It was a deliberate decision made by the maintainer. He said the chroot code in the installation was too complicated and would be removed as a part of the installation clean-up to get all BIND related files out of /usr and /etc. I protested at the time as did someone else, but the maintainer did not respond. I thnk this was a really, really bad decision. I searched a bit for the thread on removing BIND leftovers, but have failed to find it. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com