From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Users calling apache_role were not able to manage httpd_user_content_t files, directories and symbolic links.
Date: Mon, 14 Feb 2011 09:46:55 -0500 [thread overview]
Message-ID: <4D59405F.8060606@redhat.com> (raw)
In-Reply-To: <20110213175834.GA8573@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/13/2011 12:58 PM, Dominick Grift wrote:
> From 78d6e4acfc000b07dbf85b076fa523e95e72da3f Sun, 13 Feb 2011 18:55:53 +0100
> From: Dominick Grift <domg472@gmail.com>
> Date: Sun, 13 Feb 2011 18:55:09 +0100
> Subject: [PATCH] Users calling apache_role were not able to manage httpd_user_content_t files, directories and symbolic links.
>
> Users calling apache_role were not able to manage httpd_user_content_t files, directories and symbolic links.
>
> Signed-off-by: Dominick Grift <domg472@gmail.com>
>
> diff --git a/policy/modules/services/apache.if b/policy/modules/services/apache.if
> index c9e1a44..6480167 100644
> --- a/policy/modules/services/apache.if
> +++ b/policy/modules/services/apache.if
> @@ -218,10 +218,15 @@
>
> role $1 types httpd_user_script_t;
>
> - allow $2 httpd_user_content_t:{ dir file lnk_file } { relabelto relabelfrom };
> -
> allow $2 httpd_user_htaccess_t:file { manage_file_perms relabelto relabelfrom };
>
> + manage_dirs_pattern($2, httpd_user_content_t, httpd_user_content_t)
> + manage_files_pattern($2, httpd_user_content_t, httpd_user_content_t)
> + manage_lnk_files_pattern($2, httpd_user_content_t, httpd_user_content_t)
> + relabel_dirs_pattern($2, httpd_user_content_t, httpd_user_content_t)
> + relabel_files_pattern($2, httpd_user_content_t, httpd_user_content_t)
> + relabel_lnk_files_pattern($2, httpd_user_content_t, httpd_user_content_t)
> +
> manage_dirs_pattern($2, httpd_user_ra_content_t, httpd_user_ra_content_t)
> manage_files_pattern($2, httpd_user_ra_content_t, httpd_user_ra_content_t)
> manage_lnk_files_pattern($2, httpd_user_ra_content_t, httpd_user_ra_content_t)
>
>
>
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
I agree with this, Fedora Policy includes this change.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1ZQF8ACgkQrlYvE4MpobOx5gCguWyjvQNfKAjv0pn27Ux1TcH4
jioAnjTFXWcgH++LyMtJ3f9092/F69Sr
=d0SY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-14 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 17:58 [refpolicy] [PATCH] Users calling apache_role were not able to manage httpd_user_content_t files, directories and symbolic links Dominick Grift
2011-02-14 14:46 ` Daniel J Walsh [this message]
2011-02-16 14:44 ` 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=4D59405F.8060606@redhat.com \
--to=dwalsh@redhat.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.