From owner-freebsd-security  Fri Dec 18 21:02:42 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA23560
          for freebsd-security-outgoing; Fri, 18 Dec 1998 21:02:42 -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 VAA23555
          for <freebsd-security@FreeBSD.ORG>; Fri, 18 Dec 1998 21:02:41 -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 UAA64703;
	Fri, 18 Dec 1998 20:59:04 -0800 (PST)
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: "Marco Molteni" <molter@tin.it>, freebsd-security@FreeBSD.ORG
Subject: Re: A better explanation (was: buffer overflows and chroot) 
In-reply-to: Your message of "Fri, 18 Dec 1998 21:00:56 +0100."
             <11082.914011256@critter.freebsd.dk> 
Date: Fri, 18 Dec 1998 20:59:03 -0800
Message-ID: <64700.914043543@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> The basic concept is that root is only root in a jail if the filesystem
> protects the rest of the system, otherwise he isn't.  For instance he
> can change the owner or modes on a file, but he cannot change IP# on
> an interface.  He can bind to a priviledged TCP port, but only on the
> IP# which belongs to the jail.  And so forth.  Works pretty well.

I assume that this works for all devices in /dev that can either be
written to for raw access to devices or can be mmap'd for access to
various interesting parts of memory?

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message