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 1/1] Allow mount to work on all file locations
Date: Tue, 6 Sep 2011 14:36:52 -0400	[thread overview]
Message-ID: <4E666844.2040501@tresys.com> (raw)
In-Reply-To: <20110904122113.GA11786@siphos.be>

On 09/04/11 08:21, Sven Vermeulen wrote:
> In order for mount to work with all file locations, it needs
> relabelfrom privileges as well (next to the relabelto ones).
> 
> The same patch is also already present in fedora's repository.

I don't understand this, can you explain further?  This rule is for context mounts, in which it would be relabeling from any filesystem type to a file type.  When would it relabel from a file type?

> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/system/mount.te |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/policy/modules/system/mount.te b/policy/modules/system/mount.te
> index 57d7294..429596f 100644
> --- a/policy/modules/system/mount.te
> +++ b/policy/modules/system/mount.te
> @@ -77,7 +77,7 @@ files_etc_filetrans_etc_runtime(mount_t, file)
>  files_mounton_all_mountpoints(mount_t)
>  files_unmount_rootfs(mount_t)
>  # These rules need to be generalized.  Only admin, initrc should have it:
> -files_relabelto_all_file_type_fs(mount_t)
> +files_relabel_all_file_type_fs(mount_t)
>  files_mount_all_file_type_fs(mount_t)
>  files_unmount_all_file_type_fs(mount_t)
>  # for when /etc/mtab loses its type


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

  reply	other threads:[~2011-09-06 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04 12:21 [refpolicy] [PATCH 1/1] Allow mount to work on all file locations Sven Vermeulen
2011-09-06 18:36 ` Christopher J. PeBenito [this message]
2011-09-07 19:23   ` Sven Vermeulen
2011-09-08 17:12     ` Christopher J. PeBenito
2011-12-26 11:05       ` Sven Vermeulen
  -- strict thread matches above, loose matches on Subject: below --
2011-07-20 17:18 Sven Vermeulen

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=4E666844.2040501@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.