From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from jazzdrum.ncsc.mil (zombie.ncsc.mil [144.51.88.131]) by tycho.ncsc.mil (8.12.8/8.12.8) with ESMTP id k19FArXf024442 for ; Thu, 9 Feb 2006 10:10:53 -0500 (EST) Received: from tcsfw4.tcs-sec.com (jazzdrum.ncsc.mil [144.51.5.7]) by jazzdrum.ncsc.mil (8.12.10/8.12.10) with ESMTP id k19FAoL4006280 for ; Thu, 9 Feb 2006 15:10:50 GMT Message-ID: <43EB5B58.4070005@trustedcs.com> Date: Thu, 09 Feb 2006 09:10:16 -0600 From: Darrel Goeddel MIME-Version: 1.0 To: James Morris CC: "Timothy R. Chavez" , Linux Audit Discussion , James Morris , selinux@tycho.nsa.gov Subject: Re: [RFC][PATCH] collect security labels on user processes generating audit messages References: In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov James Morris wrote: > On Wed, 8 Feb 2006, Timothy R. Chavez wrote: > > >>1) A new SELinux interface was introduced to give other parts of the >>kernel the ability to resolve 'sids' into security labels. > > > Please look at the way I intend to export SELinux APIs in: > http://people.redhat.com/jmorris/selinux/skfilter/kernel/12-skfilter-selinux-exports.patch This looks good. I'm also working on some interfaces to export from selinux to enable efficient audit selection based on SELinux context and I was contemplating on exactly where to put the goods. Can we get a consensus on declaration/definition locations? "include/linux/selinux.h" and "security/selinux/exports.c" seem good to me. -- Darrel -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.