All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 7/8] Introduce rw_inherited_file_perms definition
Date: Thu, 3 Jan 2013 10:08:24 -0500	[thread overview]
Message-ID: <50E59EE8.1000803@tresys.com> (raw)
In-Reply-To: <1355737370-27628-8-git-send-email-sven.vermeulen@siphos.be>

On 12/17/12 04:42, Sven Vermeulen wrote:
> In many cases throughout the policy, domains require read/write privileges on
> inherited descriptors. In most cases, these are for files, where the domain
> needs the read-write permissions but of course no open privilege.
> 
> Instead of having to hard-code the permissions every time, this patch introduces
> the rw_inherited_file_perms to support simple calls for these inherited
> descriptors.
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/support/obj_perm_sets.spt |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/policy/support/obj_perm_sets.spt b/policy/support/obj_perm_sets.spt
> index 6e91317..48f0c7a 100644
> --- a/policy/support/obj_perm_sets.spt
> +++ b/policy/support/obj_perm_sets.spt
> @@ -158,7 +158,8 @@ define(`mmap_file_perms',`{ getattr open read execute ioctl }')
>  define(`exec_file_perms',`{ getattr open read execute ioctl execute_no_trans }')
>  define(`append_file_perms',`{ getattr open append lock ioctl }')
>  define(`write_file_perms',`{ getattr open write append lock ioctl }')
> -define(`rw_file_perms',`{ getattr open read write append ioctl lock }')
> +define(`rw_inherited_file_perms',`{ getattr read write append ioctl lock }')
> +define(`rw_file_perms',`{ rw_inherited_file_perms open }')
>  define(`create_file_perms',`{ getattr create open }')
>  define(`rename_file_perms',`{ getattr rename }')
>  define(`delete_file_perms',`{ getattr unlink }')> 

Since the tide seems to be going against me on these inherited permissions, I can accept it, but the change needs to be done for all of the relevant file classes.

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

  reply	other threads:[~2013-01-03 15:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  9:42 [refpolicy] [PATCH 0/8] Updates on master (non-contrib) Sven Vermeulen
2012-12-17  9:42 ` [refpolicy] [PATCH 1/8] Postgresql 9.2 connects to its unix stream socket Sven Vermeulen
2013-01-03 15:30   ` Christopher J. PeBenito
2012-12-17  9:42 ` [refpolicy] [PATCH 2/8] lvscan creates the /run/lock/lvm directory if nonexisting (v2) Sven Vermeulen
2013-01-03 15:30   ` Christopher J. PeBenito
2012-12-17  9:42 ` [refpolicy] [PATCH 3/8] Allow syslogger to manage cron log files (v2) Sven Vermeulen
2013-01-03 15:31   ` Christopher J. PeBenito
2012-12-17  9:42 ` [refpolicy] [PATCH 4/8] Update towards apache_manage_all_content Sven Vermeulen
2013-01-03 15:13   ` Christopher J. PeBenito
2013-01-03 16:12     ` Sven Vermeulen
2013-01-03 16:24       ` Christopher J. PeBenito
2013-01-03 16:27         ` Christopher J. PeBenito
2013-01-11 18:29           ` Dominick Grift
2013-01-11 19:23             ` Sven Vermeulen
2012-12-17  9:42 ` [refpolicy] [PATCH 5/8] Dontaudit getsched on all domains Sven Vermeulen
2012-12-17 10:20   ` grift
2012-12-17 10:26     ` Sven Vermeulen
2012-12-21 20:17       ` Sven Vermeulen
2013-01-03 15:05         ` Christopher J. PeBenito
2012-12-17  9:42 ` [refpolicy] [PATCH 6/8] Allow initrc_t to read stunnel configuration Sven Vermeulen
2013-01-03 15:31   ` Christopher J. PeBenito
2012-12-17  9:42 ` [refpolicy] [PATCH 7/8] Introduce rw_inherited_file_perms definition Sven Vermeulen
2013-01-03 15:08   ` Christopher J. PeBenito [this message]
2012-12-17  9:42 ` [refpolicy] [PATCH 8/8] Introduce exec-check interfaces for passwd binaries and useradd binaries Sven Vermeulen
2013-01-03 15:31   ` Christopher J. PeBenito

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=50E59EE8.1000803@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.