| 1 |
Ok 3rd time you have done this.. |
| 2 |
|
| 3 |
When mailing the hardened list about a given subject it helps to be more |
| 4 |
verbose with the subject lines. Being that hardened is a container |
| 5 |
project which provides several subprojects it's best add the topic of |
| 6 |
the subject in question to the Subject: of your mail. |
| 7 |
|
| 8 |
So for example if your having a problem with selinux and init.d and |
| 9 |
policy files then please use a subject such as |
| 10 |
"selinux init.d local policy question" |
| 11 |
"selinux udev security labels problem" |
| 12 |
"selinux heimdal policy" |
| 13 |
|
| 14 |
Do the same thing please if you were using grsec/PaX/rsbac/toolchain |
| 15 |
etc... |
| 16 |
|
| 17 |
thanks.. |
| 18 |
|
| 19 |
|
| 20 |
On Thu, 2006-01-19 at 10:47 +0100, Mivz wrote: |
| 21 |
> Hello, |
| 22 |
> |
| 23 |
> I have a problem with creating a init.d script and policy for a custom |
| 24 |
> daemon. |
| 25 |
> What I have: |
| 26 |
> |
| 27 |
> daemon_domain(custom) |
| 28 |
> can_exec(custom_t, custom_exec_t) |
| 29 |
> domain_auto_trans(initrc_t, custom_exec_t, custom_t) |
| 30 |
> |
| 31 |
> Also the executable and init.d script are labeld correct. |
| 32 |
> |
| 33 |
> If I call my init.d script. It say's it starts the daemon whit a nice [ |
| 34 |
> OK ], but when I check ps, there is no process. If I don't label my |
| 35 |
> script initrc_exec_t, but etc_t, it works. Except for the fact that it |
| 36 |
> uses the user context instead of |
| 37 |
> system_u:object_r because it does not use run_init. |
| 38 |
> This is all in permissive mode, so de daemon should not be blocked by |
| 39 |
> the policy. |
| 40 |
> What am I doing wrong? Why won't it work whit run_init? |
| 41 |
> |
| 42 |
> Mivz |
| 43 |
-- |
| 44 |
solar <solar@g.o> |
| 45 |
Gentoo Linux |
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-hardened@g.o mailing list |
Archives