Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 28 Jun 2002 09:18:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 28 Jun 2002 09:18:25 -0400 Received: from tomcat.admin.navo.hpc.mil ([204.222.179.33]:38937 "EHLO tomcat.admin.navo.hpc.mil") by vger.kernel.org with ESMTP id ; Fri, 28 Jun 2002 09:18:24 -0400 Date: Fri, 28 Jun 2002 08:20:13 -0500 (CDT) From: Jesse Pollard Message-Id: <200206281320.IAA77178@tomcat.admin.navo.hpc.mil> To: chris@wirex.com, Jesse Pollard Subject: Re: Status of capabilities? Cc: dax@gurulabs.com, Michael Kerrisk , linux-kernel@vger.kernel.org X-Mailer: [XMailTool v3.1.2b] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1181 Lines: 26 Chris Wright : > * Jesse Pollard (pollard@tomcat.admin.navo.hpc.mil) wrote: > > > > Actually, I think most of that work has already been done by the Linux > > Security Module project (well, except #7). > > The LSM project supports capabilities exactly as it appears in the > kernel right now. The EA linkage is still missing. Of course, we are > accepting patches ;-) Absolutely - I was just meaning that the effort of identifing the location(s) in the kernel the hooks will have to be to set the capabilities from the EA reference has been done. And in a central location too. Also, the hooks in the filesystem will provide the location, if not access to, the EA when they become available in/to the VFS (at least I hope that's where they end up). ------------------------------------------------------------------------- Jesse I Pollard, II Email: pollard@navo.hpc.mil Any opinions expressed are solely my own. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/