[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1197557461.20226.24.camel@moss-spartans.epoch.ncsc.mil>
Date: Thu, 13 Dec 2007 09:51:01 -0500
From: Stephen Smalley <sds@...ho.nsa.gov>
To: David Howells <dhowells@...hat.com>
Cc: casey@...aufler-ca.com, Karl MacMillan <kmacmill@...hat.com>,
viro@....linux.org.uk, hch@...radead.org,
Trond.Myklebust@...app.com, linux-kernel@...r.kernel.org,
selinux@...ho.nsa.gov, linux-security-module@...r.kernel.org
Subject: Re: [PATCH 08/28] SECURITY: Allow kernel services to override LSM
settings for task actions [try #2]
On Wed, 2007-12-12 at 22:55 +0000, David Howells wrote:
> Stephen Smalley <sds@...ho.nsa.gov> wrote:
>
> > More likely, run it at build time in your .spec file to generate
> > cachefiles.conf,
>
> I don't think sticking it in cachefiles.conf is a good idea necessarily.
> That has to be an administrator modifiable file. Is there a program I could
> make cachefiles run directly and capture the output of that could give me the
> info I want?
Yes, we could easily make a simple program that just invokes a
libselinux function that in turn grabs the proper context from some
context configuration file under /etc/selinux/$SELINUXTYPE/contexts/ and
outputs it. Dan can help with that.
> > then run it again maybe upon a policy update or if the user selects a
> > different policy.
>
> How do I do that?
--
Stephen Smalley
National Security Agency
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists