From owner-freebsd-security Fri Dec 18 20:57:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23307 for freebsd-security-outgoing; Fri, 18 Dec 1998 20:57:57 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23302 for ; Fri, 18 Dec 1998 20:57:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id UAA64691; Fri, 18 Dec 1998 20:57:52 -0800 (PST) To: "Marco Molteni" cc: freebsd-security@FreeBSD.ORG Subject: Re: A better explanation (was: buffer overflows and chroot) In-reply-to: Your message of "Fri, 18 Dec 1998 19:57:07 +0100." Date: Fri, 18 Dec 1998 20:57:52 -0800 Message-ID: <64687.914043472@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Scenario: > > [all reasonable points elided] > 5. I want to put him in a chroot jail full of suid binaries, but suid > not to root, to pseudoroot, where pseudoroot is a non privileged user. That won't work, however, since he can still "break out" of the chroot jail very easily, especially if he's someone who "knows his stuff" as you seem to indicate. It's a jail with paper mache' bars, nothing more. I still think he needs his own machine, full stop. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message