Research
Skip Research Menus
Research MenuSecurity Enhanced Linux What's New Frequently Asked Questions Background Documents License Download Participating Mail List Archives Remaining Work Contributors Related Work Press Releases Information Assurance Research NIARL In-house Research Areas Mathematical Sciences Program Sabbaticals Computer & Information Sciences Research Technology Transfer Advanced Computing Advanced Mathematics Communications & Networking Information Processing Microelectronics Other Technologies Technology Fact Sheets Publications Related Links |
SELinux Mailing ListRe: [PATCH 08/28] SECURITY: Allow kernel services to override LSM settings for task actions [try #2]
From: David Howells <dhowells_at_redhat.com>
Date: Wed, 19 Dec 2007 23:38:27 +0000
> > This is used, for example, by CacheFiles which has to transparently access NFS Daemon? NFS quite often runs in the context of whichever process issued, say, a read syscall. It's at this point the cachefiles needs to run, and using change_profile is I suspect not an option there. Remember: you can't change the objective profile of the aforementioned process, hence the act_as pointer. That said, I don't know what change_profile does.
> However, it seems to me that you have the same problem with SELinux: I'm not sure what you're getting at. The security NFS uses to access the server is separate from the security that cachefiles uses to access the cache.
> > How about I just stick the context in /etc/cachefilesd.conf as a textual Okay.
> It would be easier if you did that in user space instead of in the kernel, Do what in userspace? Parse the context? Validate the context? Or change the context?
> I don't know if it causes a problem to attempt to kind-of call The cache aborts and all subsequent operations on that cache bounce and go to the server instead. The change of context cannot be done in userspace because to get to a userspace capable of attempting this operation would itself require a change of context. Besides, it'd also be inefficient, probably horribly so, to do all caching ops in userspace. What I need is an LSM operation to change a task_security struct to have a specified context. I can then use the task_security struct in all future cache ops on a cache by pointing task->act_as at it. David -- 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.Received on Wed 19 Dec 2007 - 18:39:48 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |