All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Any word on updating the base so we can start pushing fixes into contrib?
Date: Thu, 15 Dec 2011 08:54:20 -0500	[thread overview]
Message-ID: <4EE9FC0C.6090009@tresys.com> (raw)
In-Reply-To: <4EE7B685.1090300@redhat.com>

On 12/13/11 15:33, Daniel J Walsh wrote:
> On 12/13/2011 02:02 PM, Christopher J. PeBenito wrote:
>> Which patch(es) are blocking that?
> 
> Add new attributes to define a domain as an homedirreader or
> homedirwriter.

I don't agree with the homedirreader and homedirwriter concepts.  I think the appropriate way is to abstract all of this noxattr home dir access is to do this for all of the existing interfaces.  I would have done this in the first place, if there wasn't the problem with nested conditionals.

So for example, take userdom_list_user_home_content.  The ideal would be

interface(`userdom_list_user_home_content',`
        gen_require(`
                type user_home_t;
        ')

        allow $1 user_home_t:dir list_dir_perms;

        tunable_policy(`use_nfs_home_dirs',`
                fs_read_nfs_files($1)
        ')

        tunable_policy(`use_samba_home_dirs',`
                fs_read_cifs_files($1)
        ')
')

But since this would cause problems if calls to this interface were in a conditional, we couldn't do this.  I'd be fine taking an attribute style implementation like you have in this patch, but it would have to be for all of the relevant existing interfaces.  That should have the benefit of eliminating all of the use_nfs_home_dirs and use_samba_home_dirs strewn all over the policy.  If you skip the relabel, filetrans, domtrans, and dontaudit interfaces, I came up with 19 interfaces.


> New Policy for sblim
> New policy for glance from fedora
> New policy for matahari

I've merged these.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2011-12-15 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 18:53 [refpolicy] Any word on updating the base so we can start pushing fixes into contrib? Daniel J Walsh
2011-12-13 19:02 ` Christopher J. PeBenito
2011-12-13 20:33   ` Daniel J Walsh
2011-12-15 13:54     ` Christopher J. PeBenito [this message]
2011-12-15 14:56       ` Daniel J Walsh
2011-12-16 15:29         ` Christopher J. PeBenito
2011-12-15 19:10       ` Daniel J Walsh

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=4EE9FC0C.6090009@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=refpolicy@oss.tresys.com \
    /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.