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