From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965138AbWECJZZ (ORCPT ); Wed, 3 May 2006 05:25:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965136AbWECJZZ (ORCPT ); Wed, 3 May 2006 05:25:25 -0400 Received: from zeus1.kernel.org ([204.152.191.4]:44753 "EHLO zeus1.kernel.org") by vger.kernel.org with ESMTP id S965133AbWECJZZ (ORCPT ); Wed, 3 May 2006 05:25:25 -0400 Date: Mon, 1 May 2006 20:56:17 +0000 From: Pavel Machek To: Jan Engelhardt Cc: Greg KH , Arjan van de Ven , James Morris , Christoph Hellwig , Andrew Morton , Stephen Smalley , T?r?k Edwin , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Wright , Linus Torvalds Subject: Re: [PATCH 0/4] MultiAdmin LSM Message-ID: <20060501205617.GA4645@ucw.cz> References: <20060417173319.GA11506@infradead.org> <20060417195146.GA8875@kroah.com> <1145462454.3085.62.camel@laptopd505.fenrus.org> <20060419201154.GB20545@kroah.com> <20060421150529.GA15811@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > Subject: [PATCH 0/4] MultiAdmin LSM > (was: Re: Time to remove LSM > (was: Re: [RESEND][RFC][PATCH 2/7] implementation of LSM hooks)) > > > 0. Preface > ========== > Thanks to Greg who, requiring me to post more-split patches, made me > reconsider the code. I did nothing less than to simplified the whole patch > cruft (shrunk by factor 10) and removed what seemed unreasonable. This > thread posts MultiAdmin *1.0.5*. > > > > 1. Super-short description > ========================== > Three user classes exist (determined by user-defined UID ranges), > - superadmin, the usual "root" > - subadmin > - normal users > > A usual (non-multiadm,non-selinux) system has only one superadmin (UID 0) > and a number of normal users, and the superadmin can operate on > everything. > > The "subadmin" can read in some superadmin-only places, and is allowed to > fully operate on processes/files/ipc/etc. of normal users. The full list > (possibly incomplete) of permissions is available in the README.txt > (includes short description) in the out-of-tree tarball. > [http://freshmeat.net/p/multiadm/] I guess you should really split CAP_SYS_ADMIN into some subsets that make sense... along with explanation why subsets are 'right'. Pavel -- Thanks, Sharp!