From: Daniel J Walsh <dwalsh@redhat.com>
To: michel m <michel.mcgregor@gmail.com>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: domain transition issue
Date: Tue, 09 Mar 2010 11:27:13 -0500 [thread overview]
Message-ID: <4B9676E1.1000905@redhat.com> (raw)
In-Reply-To: <bb74313d1003090553k3e3d092ep619f337a8591670@mail.gmail.com>
On 03/09/2010 08:53 AM, michel m wrote:
> Hello,
> I need to run an unconfined process in a confined domain, say httpd_t.
> To do so, I changed executable file's context to a confined one, say
> httpd_exec_t, but after running it, its process was in unconfined
> domain again.
> As I searched more, I found that there is not a legal transition for
> an unconfined process to a confined one in normal form. I created an
> script file which contained scripts for running my desired
> application, changed script's context to initrc_exec_t. after running
> this script, I get my process unconfined again.
> may some one guide me how to resolve this issue and run my application
> is unconfined domain?
>
> Regards.
If you want to transition from unconfined_t to httpd_t you need to
execute a script labeled initrc_exec_t.
unconfined_t -> initrc_exec_t -> initrc_t -> httpd_exec_t -> httpd_t
So you need the init script labeled initrc_exec_t and the program you
want to run as httpd_t to be labeled httpd_exec_t.
I would add an id -Z to your initrc_exec_t script to make sure the
transition happened.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2010-03-09 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 13:53 domain transition issue michel m
2010-03-09 16:27 ` Daniel J Walsh [this message]
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=4B9676E1.1000905@redhat.com \
--to=dwalsh@redhat.com \
--cc=michel.mcgregor@gmail.com \
--cc=selinux@tycho.nsa.gov \
/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.