Re: run_init woes

[Tom <tom@lemuria.org>]

On Thu, May 22, 2003 at 08:10:20AM -0400, Stephen Smalley wrote:
> What happens if you do the following (in permissive mode, of course):
> 	runas system_u:system_r:initrc_t /etc/init.d/pxe start

It starts up and runs in the correct domain. (pxe_t)


> Are you using the extension to run_init created by Russell Coker to
> create a separate pty for the daemon, or just the normal run_init
> program?  

I'm using Russells run_init from his current debian packages. I assume
that it comes with his extensions.



> What happens if you use the upstream run_init without his
> modification?   

I've just downloaded and compiled it, and it works fine.

Russell - I've also made a few other experiments, since I was so sure I
had seen this before. rsync (as a daemon) also has the same problem,
but it throws an error message into the logfile:

May 22 15:27:38 setest rsyncd[681]: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)


It also works fine with the upstream run_init. Of course, there are
these messages which were the initial cause for the modification:

May 22 15:28:13 setest kernel: avc:  denied  { read write } for  pid=688 exe=/usr/bin/rsync path=/0 dev=00:07 ino=2 scontext=system_u:system_r:rsyncd_t tcontext=root:object_r:user_devpts_t tclass=chr_file


-- 
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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.