From: sds@tycho.nsa.gov (Stephen Smalley)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Defining per-service initrc domains
Date: Thu, 09 Dec 2010 14:49:37 -0500 [thread overview]
Message-ID: <1291924177.30609.17.camel@moss-pluto> (raw)
In-Reply-To: <06A6610D4F464D4EBEAFBF2C5F86911E0265270F@exchange2.columbia.tresys.com>
On Tue, 2010-12-07 at 11:20 -0500, Jeremy Solt wrote:
> Hi Stephen,
>
> I know it's been a while, but were you able to get this working
> correctly? If not, I need some clarification. Were you trying to go from
> init_t directly to ftpd_initrc_t over ftpd_initrc_exec_t (skipping
> initrc_t completely)? Or just init_t -> initrc_t -> ftpd_initrc_t ->
> ftpd_t ?
>
> I ran some tests on init_script_domain(). On a Fedora 13 system, I
> tested this out with qpidd and saw the following transitions:
> init_t -> initrc_t -> qpidd_initrc_t -> qpidd_t
>
> On a RHEL 5 system, I installed reference policy (to make sure the
> problem hadn't been fixed by Dan in Fedora's patches) and tried this
> with the ntp daemon. My transitions:
> init_t -> initrc_t ->ntpd_initrc_t -> ntpd_t
>
> Is this the path you were looking for or am I misunderstanding the
> problem?
That sounds right, but it didn't seem to work for us. We were trying it
for the hadoop policy that has subsequently been merged, in order to get
the hadoop daemons into the right domains.
--
Stephen Smalley
National Security Agency
next prev parent reply other threads:[~2010-12-09 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:57 [refpolicy] Defining per-service initrc domains Stephen Smalley
2010-07-14 11:48 ` Russell Coker
2010-07-14 13:40 ` Stephen Smalley
2010-07-19 18:05 ` Christopher J. PeBenito
2010-12-07 16:20 ` Jeremy Solt
2010-12-09 19:49 ` Stephen Smalley [this message]
2010-12-09 22:10 ` Paul Nuzzi
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=1291924177.30609.17.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--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.