From owner-freebsd-security  Sun Nov 17 14:29:37 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA18557
          for security-outgoing; Sun, 17 Nov 1996 14:29:37 -0800 (PST)
Received: from garrison.inetcan.net (dreamer@garrison.inetcan.net [206.186.215.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18515
          for <freebsd-security@freebsd.org>; Sun, 17 Nov 1996 14:28:45 -0800 (PST)
Received: (from dreamer@localhost) by garrison.inetcan.net (8.7.6/8.7.3) id PAA01894; Sun, 17 Nov 1996 15:31:16 -0700
Date: Sun, 17 Nov 1996 15:31:15 -0700 (MST)
From: Digital Dreamer <dreamer@garrison.inetcan.net>
To: "az.com" <yankee@lucy.az.com>
cc: freebsd-security@freebsd.org
Subject: Re: grand alternatives to chroot, solution to the age-old root problem
In-Reply-To: <Pine.BSF.3.91.961117133249.19647K-100000@lucy.az.com>
Message-ID: <Pine.LNX.3.91.961117152955.1880A-100000@garrison.inetcan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 17 Nov 1996, az.com wrote:

> No longer do you have to worry about whether they have root or not - in
> fact each user gets to be root! (in their own machine, of course ;) ) If
> they want to hack, get fancy, reboot, etc. - its up to them - its *their*
> system, not yours. 
> 
> If they blow out the virtual OS space because they gave their password out
> to a grommet or made a mistake, you simply run a utility which checks and
> repairs virtual file system's partitions and refreshes the virtual
> 'environment's' OS from a template. 

Sounds nice, but kind of impractical.  There's no unice (AFAIK) whose 
kernel could do this without essentially being rewritten.  Besides, 
there's still the possibility of kernel bugs that would let you break out 
of your vm and get into that of others.

dreamer