From: Janak Desai <janak@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: gyurdiev@redhat.com, janak@us.ibm.com,
Karl MacMillan <kmacmillan@tresys.com>,
selinux@tycho.nsa.gov, "'Daniel J Walsh'" <dwalsh@redhat.com>
Subject: Re: file contexts and modularity
Date: Wed, 29 Jun 2005 16:13:45 -0400 [thread overview]
Message-ID: <42C300F9.2030701@us.ibm.com> (raw)
In-Reply-To: <1120074657.3553.217.camel@moss-spartans.epoch.ncsc.mil>
Yes, I am continuing the work started by Chad Sellers. I am working with
the new unshare system call and using pam session management hooks to
setup and reset namespace from session creating programs. I am
currently unit testing/debugging the stuff and am hoping to post the
pam patches here in about a week or so.
-Janak
Stephen Smalley wrote:
> On Wed, 2005-06-29 at 15:24 -0400, Ivan Gyurdiev wrote:
>
>>Can you explain how this would work a bit?
>>How would matchpathcon work on a polyinstantiated directory?
>
>
> I'm not sure what you are asking. Basic concept is that the user
> actually has a separate home directory (and /tmp and whatever else) per
> role, and the right one is automatically bind mounted onto their
> official home directory location at login time (and adjusted as needed
> upon su, newrole, etc). The code allows for dynamic creation of those
> per-role home directories on demand, e.g. when the user logs in at a
> given role, but of course, that will leave them with an empty directory
> at present. We would need to deal with setup, e.g. initial copying of
> skeleton files when the per-role directory is first created, which could
> be handled at login time. Chad Sellers posted example patches earlier
> for login, gdm, and su. Implementation would be greatly simplified by
> unshare(2) call, which would allow handling it in libpam rather than
> patching each login-like program - Janak was working on such a patch.
> Current implementation creates the per-role directories as
> subdirectories of the official home directory location, but others have
> suggested making that location configurable.
>
> So at that point you no longer need to keep home directory contexts in
> file_contexts at all, and you just exclude home directories from
> relabeling.
>
--
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.
next prev parent reply other threads:[~2005-06-29 20:13 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 3:00 file contexts and modularity Ivan Gyurdiev
2005-06-23 17:37 ` Karl MacMillan
2005-06-23 18:05 ` Ivan Gyurdiev
2005-06-23 18:21 ` Karl MacMillan
2005-06-23 18:25 ` Ivan Gyurdiev
2005-06-23 18:40 ` Karl MacMillan
2005-06-23 19:00 ` Ivan Gyurdiev
2005-06-23 19:39 ` Karl MacMillan
2005-06-23 20:28 ` Ivan Gyurdiev
2005-06-23 20:36 ` Ivan Gyurdiev
2005-06-24 12:08 ` Stephen Smalley
2005-06-24 15:43 ` Ivan Gyurdiev
2005-06-24 18:32 ` Stephen Smalley
2005-06-24 18:37 ` Ivan Gyurdiev
2005-06-24 12:21 ` Stephen Smalley
2005-06-24 14:30 ` Karl MacMillan
2005-06-24 16:05 ` Karl MacMillan
2005-06-24 18:05 ` Frank Mayer
2005-06-24 18:40 ` Stephen Smalley
2005-06-28 15:41 ` Karl MacMillan
2005-06-28 16:21 ` Stephen Smalley
2005-06-24 15:51 ` Casey Schaufler
2005-06-24 16:36 ` Karl MacMillan
2005-06-24 16:47 ` Casey Schaufler
2005-06-24 16:56 ` Karl MacMillan
2005-06-24 17:10 ` Casey Schaufler
2005-06-24 15:39 ` Karl MacMillan
2005-06-24 16:03 ` Ivan Gyurdiev
2005-06-24 16:28 ` Karl MacMillan
2005-06-24 17:56 ` Ivan Gyurdiev
2005-06-27 15:07 ` Karl MacMillan
2005-06-27 15:36 ` Ivan Gyurdiev
2005-06-27 17:25 ` Karl MacMillan
2005-06-27 17:56 ` Ivan Gyurdiev
2005-06-28 13:47 ` Karl MacMillan
2005-06-28 19:31 ` Ivan Gyurdiev
2005-06-29 17:28 ` Ivan Gyurdiev
2005-06-29 18:17 ` Karl MacMillan
2005-06-29 18:46 ` Ivan Gyurdiev
2005-06-29 18:53 ` Stephen Smalley
2005-06-29 19:04 ` Karl MacMillan
2005-06-29 19:24 ` Ivan Gyurdiev
2005-06-29 19:50 ` Stephen Smalley
2005-06-29 20:03 ` Ivan Gyurdiev
2005-06-29 20:09 ` Stephen Smalley
2005-06-29 20:22 ` Ivan Gyurdiev
2005-06-30 13:54 ` Stephen Smalley
2005-06-29 20:22 ` Janak Desai
2005-06-29 20:43 ` Ivan Gyurdiev
2005-06-30 13:53 ` Ivan Gyurdiev
2005-06-30 13:58 ` Stephen Smalley
2005-06-30 14:48 ` Karl MacMillan
2005-06-30 14:52 ` Stephen Smalley
2005-06-30 13:56 ` Stephen Smalley
2005-06-29 20:13 ` Janak Desai [this message]
2005-06-30 0:40 ` Luke Kenneth Casson Leighton
2005-06-29 19:04 ` Karl MacMillan
2005-06-29 19:20 ` Ivan Gyurdiev
2005-06-24 5:03 ` Ivan Gyurdiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42C300F9.2030701@us.ibm.com \
--to=janak@us.ibm.com \
--cc=dwalsh@redhat.com \
--cc=gyurdiev@redhat.com \
--cc=kmacmillan@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.