From owner-freebsd-hackers Mon Sep 25 11:07:23 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA18263 for hackers-outgoing; Mon, 25 Sep 1995 11:07:23 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA18250 for ; Mon, 25 Sep 1995 11:06:55 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA05460; Mon, 25 Sep 1995 11:02:38 -0700 From: Terry Lambert Message-Id: <199509251802.LAA05460@phaeton.artisoft.com> Subject: Re: FreeBSD Questions To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 25 Sep 1995 11:02:38 -0700 (MST) Cc: gcrutcher@datatrek.com, hackers@FreeBSD.ORG In-Reply-To: <199509250711.IAA06270@uriah.heep.sax.de> from "J Wunsch" at Sep 25, 95 08:11:01 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 467 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > The only safe environment for such a case is setting up a chroot > environment. It's a bit more work, but you can have a better feeling > after you're done. :-) And there's a nice large hole in that, too, if you have any directory hard links or fd's open to directories without close on exec set (or implied by the chroot). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.