From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v3 0/3] Support read/append/manage functions for various httpd content
Date: Sun, 24 Jun 2012 13:07:36 +0200 [thread overview]
Message-ID: <20120624110736.GA995@siphos.be> (raw)
Within this patch set, we make the web content types as defined by the apache
module more generic in use so that other domains, who need to interact with
these types, can do so without getting too many privileges assigned (like with
apache_manage_all_content).
Since v2, the following changes have been incorporated:
- Use double comment for phpfpm's summary
Since v1, the following changes have been incorporated:
- Adding apache_search_all_content within the apache_append_all_ra_content_files
interface
- Adding phpfpm_t domain as an example user for these interfaces
With thanks to Dominick Grift for his feedback.
next reply other threads:[~2012-06-24 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 11:07 Sven Vermeulen [this message]
2012-06-24 11:08 ` [refpolicy] [PATCH v3 1/3] Support read/append/manage functions for various httpd content Sven Vermeulen
2012-06-26 13:22 ` Christopher J. PeBenito
2012-06-26 13:57 ` Dominick Grift
2012-06-26 14:04 ` Christopher J. PeBenito
2012-06-26 20:38 ` Sven Vermeulen
2012-06-26 21:10 ` Dominick Grift
2012-06-27 14:17 ` Christopher J. PeBenito
2012-06-27 14:31 ` Christopher J. PeBenito
2012-06-24 11:08 ` [refpolicy] [PATCH v3 2/3] Introducing phpfpm_t domain Sven Vermeulen
2012-06-26 13:29 ` Christopher J. PeBenito
2012-06-24 11:09 ` [refpolicy] [PATCH v3 3/3] Allow sysadm_t to administer phpfpm environment 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=20120624110736.GA995@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.