From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262590AbTJAVRF (ORCPT ); Wed, 1 Oct 2003 17:17:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262591AbTJAVRF (ORCPT ); Wed, 1 Oct 2003 17:17:05 -0400 Received: from fw.osdl.org ([65.172.181.6]:35274 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262590AbTJAVRC (ORCPT ); Wed, 1 Oct 2003 17:17:02 -0400 Date: Wed, 1 Oct 2003 14:16:54 -0700 From: Chris Wright To: Chris Wright , Rik van Riel , torvalds@osdl.org, greg@kroah.com, linux-kernel@vger.kernel.org, vserver@solucorp.qc.ca Subject: Re: sys_vserver Message-ID: <20031001141654.N14398@osdlab.pdx.osdl.net> References: <20031001115127.A14425@osdlab.pdx.osdl.net> <20031001121536.J14398@osdlab.pdx.osdl.net> <20031001194747.GA24632@DUK2.13thfloor.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20031001194747.GA24632@DUK2.13thfloor.at>; from herbert@13thfloor.at on Wed, Oct 01, 2003 at 09:47:47PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Herbert Poetzl (herbert@13thfloor.at) wrote: > > one of the advantages the current _and_ future vserver project > has over 'changing/setting some features for a process' is the > concept of a context layer, residing between kernel and processes > _belonging_ to a context ... Yes, I agree, this is a useful abstraction. > you could, for example set up a context which allows a maximum > of 10 processes, limited to one ethernet interface, using it's > own root/user quota, start some 'virtual' server in this context > doing all this init stuff, and then visit this context from > outside, via a simple 'context' change ... if you've got the > right capabilities/permissions ... > > I can not imagine how you would do that with the /proc//attr/ > interface, but I'm sure you can explain it to me ... Put it this way, typical security modules have a notion of a context, and the ability to grant/deny actions base on the context. The /proc//attr interface is how you can set/retrieve the context per process, and subsequent fork/exec's can chose how to propagate that context. I believe a reasonable portion of vserver can become a security module, but there would clearly remain a need for some of the virtualization (e.g. hostname, etc.). thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net