From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC] Reintroduce httpd_user_content_type and httpd_user_script_exec_type attributes
Date: Mon, 11 Feb 2013 20:33:54 +0100 [thread overview]
Message-ID: <20130211193354.GA12406@siphos.be> (raw)
In-Reply-To: <1360611019.2559.22.camel@d30>
On Mon, Feb 11, 2013 at 08:30:19PM +0100, Dominick Grift wrote:
> > The httpd_user_content_type and httpd_user_script_exec_type attributes were
> > erroneously removed a while ago, but while trying to reintroduce them I did
> > notice that they were removed because there was no way for users to actually
> > use them (or I'm completely misreading the policy code).
>
> I still do not understand the purpose of this. Is there some actual need
> for this? I deprecated the interface because it was unused and i could
> not see a convincing need for it to exist.
>
> Can you enlighten me? What issue are you facing? Who, other than the
> user needs to be able to manage user content/script dirs, files and
> symlinks?
I'll have to ask Christopher, I made this patch as a result of our previous
thread on this matter (where I initially changed a deprecated function to
reflect the removal of these types):
http://oss.tresys.com/pipermail/refpolicy/2013-January/006255.html
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2013-02-11 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 19:02 [refpolicy] [PATCH/RFC] Reintroduce httpd_user_content_type and httpd_user_script_exec_type attributes Sven Vermeulen
2013-02-11 19:30 ` Dominick Grift
2013-02-11 19:33 ` Sven Vermeulen [this message]
2013-02-11 19:51 ` Dominick Grift
2013-02-11 19:56 ` Dominick Grift
2013-02-11 20:03 ` Dominick Grift
2013-02-11 22:35 ` 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=20130211193354.GA12406@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.