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 v2 1/2] Allow all domains to read /proc/sys/vm/overcommit_memory
Date: Thu, 14 Aug 2014 15:29:28 -0400	[thread overview]
Message-ID: <53ED0E18.1050500@tresys.com> (raw)
In-Reply-To: <1407005263-3144-2-git-send-email-gentoo+selinux@lerya.net>

On 8/2/2014 2:47 PM, Vincent Brillault wrote:
> From: Dan Walsh <dwalsh@redhat.com>
> 
> glibc malloc read this file since commit 9fab36eb
> (https://sourceware.org/git/?p=glibc.git;a=commit;h=9fab36eb)
> 
> Patch adapted from commit 343c0887514718387f36ee8ead2b941ba9bfb894
> on fedora selinux-policy
> 
> Signed-off-by: Vincent Brillault <git@lerya.net>
> ---
>  policy/modules/kernel/domain.te |  4 +++
>  policy/modules/kernel/kernel.if | 57 +++++++++++++++++++++++++++++++++++++++++
>  policy/modules/kernel/kernel.te |  4 +++
>  3 files changed, 65 insertions(+)
> 
> diff --git a/policy/modules/kernel/domain.te b/policy/modules/kernel/domain.te
> index 4af7dbd..b95c75d 100644
> --- a/policy/modules/kernel/domain.te
> +++ b/policy/modules/kernel/domain.te
> @@ -99,6 +99,10 @@ allow domain self:process { fork sigchld };
>  # glibc get_nprocs requires read access to /sys/devices/system/cpu/online
>  dev_read_cpu_online(domain)
>  
> +# glibc malloc requires access to /proc/sys/vm/overcommit_memory
> +# see https://sourceware.org/git/?p=glibc.git;a=commit;h=9fab36eb
> +kernel_read_vm_overcommit_sysctls(domain)

This set of lines should go higher than dev_read_cpu_online().


> +interface(`kernel_read_vm_overcommit_sysctls',`
> +	gen_require(`
> +		type proc_t, sysctl_t, sysctl_vm_overcommit_t;
> +	')
> +
> +	read_files_pattern($1, { proc_t sysctl_t sysctl_vm_overcommit_t }, sysctl_vm_overcommit_t)
> +')
[...]
> +interface(`kernel_rw_vm_overcommit_sysctls',`
> +	gen_require(`
> +		type proc_t, sysctl_t, sysctl_vm_overcommit_t;
> +	')
> +
> +	rw_files_pattern($1 ,{ proc_t sysctl_t sysctl_vm_overcommit_t }, sysctl_vm_overcommit_t)
> +	list_dirs_pattern($1, { proc_t sysctl_t }, sysctl_vm_overcommit_t)
> +')

These two interfaces are overspecified.  sysctl_vm_overcommit_t
shouldn't be included in the second parameter of the patterns
(read_files_pattern and rw_files_pattern) since the type is never used
on a directory.

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

  reply	other threads:[~2014-08-14 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 18:35 [refpolicy] [PATCH 0/2] Give access to /proc/sys/vm/overcommit_memory to all domains Vincent Brillault
2014-08-02 18:35 ` [refpolicy] [PATCH 1/2] Allow all domains to read /proc/sys/vm/overcommit_memory Vincent Brillault
2014-08-02 18:35 ` [refpolicy] [PATCH 2/2] Extend kernel_search_*_overcommit_sysctl search Vincent Brillault
2014-08-02 18:47 ` [refpolicy] [PATCH v2 0/2] Give access to /proc/sys/vm/overcommit_memory to all domains Vincent Brillault
2014-08-02 18:47   ` [refpolicy] [PATCH v2 1/2] Allow all domains to read /proc/sys/vm/overcommit_memory Vincent Brillault
2014-08-14 19:29     ` Christopher J. PeBenito [this message]
2014-08-14 19:47       ` Dominick Grift
2014-08-14 19:59         ` Christopher J. PeBenito
2014-08-02 18:47   ` [refpolicy] [PATCH v2 2/2] Extend kernel_search_*_overcommit_sysctl search Vincent Brillault

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=53ED0E18.1050500@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.