Date: Sat, 15 Jun 2002 16:33:03 -0700 (PDT) From: Brett Glass <brett@lariat.org> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/39355: Sandboxing BIND difficult and error-prone Message-ID: <200206152333.g5FNX3aS098177@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 39355 >Category: bin >Synopsis: Sandboxing BIND difficult and error-prone >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jun 15 16:40:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Brett Glass >Release: All recent releases >Organization: >Environment: >Description: The procedure for sandboxing BIND, as listed in the FreeBSD Handbook, requires files to be moved, permissions to be changed, directories to be created, configuration changes to be made.... All by hand. There are more than 20 steps to perform on 4.x out of the box, all fraught with potential errors. >How-To-Repeat: I can never repeat the problem exactly, because I make a different typo every time. ;-) >Fix: Ideally, the default install would be set up so that BIND was sandboxed from the get-go, or (at least) so that one could throw a switch in rc.conf to make it happen. Who maintains the BIND that's bundled with FreeBSD? Can we make this happen? >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206152333.g5FNX3aS098177>