Ok 3rd time you have done this.. When mailing the hardened list about a given subject it helps to be more verbose with the subject lines. Being that hardened is a container project which provides several subprojects it's best add the topic of the subject in question to the Subject: of your mail.
So for example if your having a problem with selinux and init.d and policy files then please use a subject such as "selinux init.d local policy question" "selinux udev security labels problem" "selinux heimdal policy" Do the same thing please if you were using grsec/PaX/rsbac/toolchain etc... thanks.. On Thu, 2006-01-19 at 10:47 +0100, Mivz wrote: > Hello, > > I have a problem with creating a init.d script and policy for a custom > daemon. > What I have: > > daemon_domain(custom) > can_exec(custom_t, custom_exec_t) > domain_auto_trans(initrc_t, custom_exec_t, custom_t) > > Also the executable and init.d script are labeld correct. > > If I call my init.d script. It say's it starts the daemon whit a nice [ > OK ], but when I check ps, there is no process. If I don't label my > script initrc_exec_t, but etc_t, it works. Except for the fact that it > uses the user context instead of > system_u:object_r because it does not use run_init. > This is all in permissive mode, so de daemon should not be blocked by > the policy. > What am I doing wrong? Why won't it work whit run_init? > > Mivz -- solar <[EMAIL PROTECTED]> Gentoo Linux -- [email protected] mailing list
