All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Edenfield <kutulu@kutulu.org>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SELinux Mailing List <selinux@tycho.nsa.gov>
Subject: Re: [refpolicy patch, second try] samba policy updates
Date: Thu, 31 Jul 2008 14:24:52 -0400	[thread overview]
Message-ID: <48920374.50508@kutulu.org> (raw)
In-Reply-To: <1217527566.4114.59.camel@gorn.columbia.tresys.com>

Christopher J. PeBenito wrote:
> On Thu, 2008-07-31 at 12:27 -0400, Mike Edenfield wrote:
>> Christopher J. PeBenito wrote:
>>
>>> Interfaces should not have side effects.  If you have a create interface
>>> and it does something else like filetrans, filetrans is a side effect.
>>> The tunable should be:
>>>
>>> tunable_policy(
>>>   unprivuser_create_home_dirs()
>>>   unprivuser_home_filetrans_home_dir()
>>> )
>> Ok, I think I get it now.  Sorry for being kinda dense :)
>>
>> So, what I should have dome is something like this:
>>
>> tunable_policy (
>>    unprivuser_home_filetrans_home_dir()
>>    unprivuser_create_home_dir()
>>    unprivuser_add_entry_home_dir()
>> )
>>
>>
>> with two new interfaces:
>>
>> unprivuser_create_home_dir (
>>    allow user_home_dir_t:dir create_dir_perms
>> )
>>
>> unprivuser_add_entry_home_dir (
>>    allow user_home_dir_t:dir add_entry_dir_perms
>> )
> 
> Why do you need the add_entry?  You just want to create
> the /home/foouser directory right?  Add_entry is for when you want to
> create an object in that type of directory.

Well, I do actually want to create objects in the new home directory. 
It needs to be populated from /etc/skel (which the PAM module does 
automatically).

But it turns out that the existing samba policy already takes care of 
this, *if* you also turn on "enable_home_dirs", so its not needed here. 
  It does mean that the "create" tunable, without the "enable" tunable, 
creates an empty home directory, which I was trying to minimize.  But as 
I think about it, it probably doesn't make sense to have Samba create 
user home directories if you're not going to allow Samba to share them 
out, so it's probably ok.

New patch coming up.

--Mike


--
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.

      reply	other threads:[~2008-07-31 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 16:00 [refpolicy patch, second try] samba policy updates Mike Edenfield
2008-07-29 14:47 ` Chris PeBenito
2008-07-29 17:38   ` Mike Edenfield
2008-07-29 19:54     ` Chris PeBenito
2008-07-29 21:22       ` Mike Edenfield
2008-07-31 12:56         ` Christopher J. PeBenito
2008-07-31 16:27           ` Mike Edenfield
2008-07-31 18:06             ` Christopher J. PeBenito
2008-07-31 18:24               ` Mike Edenfield [this message]

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=48920374.50508@kutulu.org \
    --to=kutulu@kutulu.org \
    --cc=cpebenito@tresys.com \
    --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.