From owner-freebsd-stable Thu Feb 1 10:32: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3415A37B4EC for ; Thu, 1 Feb 2001 10:31:48 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id TAA31864; Thu, 1 Feb 2001 19:31:44 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Stefan Molnar Cc: Gordon Tetlow , Vivek Khera , Subject: Re: chrooting bind References: From: Dag-Erling Smorgrav Date: 01 Feb 2001 19:31:43 +0100 In-Reply-To: Stefan Molnar's message of "Thu, 1 Feb 2001 10:26:44 -0800 (PST)" Message-ID: Lines: 20 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Molnar writes: > I see where you are coming from now. On this system I attempted > to be more complete, basicly give it everything That totally defeats the point of running in a sandbox. > and attempt to > depend on nothing outside the sandbox. The point is to have as little as possible inside the sandbox. You need named-xfer if you have slave zones, but you do not need any other binaries, you do not need any libraries (link named-xfer statically!) and you certainly don't need any device nodes. ANYTHING YOU PUT IN THE SANDBOX WILL BE AVAILABLE TO INTRUDERS WHEN THEY BREAK INTO YOUR SYSTEM. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message