1 |
On Sun, 2008-03-09 at 09:43 -0400, Mike Edenfield wrote: |
2 |
> I've almost got my wpa policy module working properly, but something I |
3 |
> did along the way is causing the startup scripts to act kinda strange. |
4 |
> The wpa processes are now running under the domain I defined for them, |
5 |
> but so are a bunch of other network daemon processes that launch after WPA: |
6 |
> |
7 |
> system_u:system_r:wpa_t 3944 ? Ss 0:00 /sbin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -C/var/run |
8 |
> system_u:system_r:wpa_t 3955 ? Ss 0:00 /bin/wpa_cli -a/etc/wpa_supplicant/wpa_cli.sh -p/var/run/wpa_supplicant - |
9 |
> system_u:system_r:wpa_t 6834 ? Ss 0:00 sshd: kutulu [priv] |
10 |
> system_u:system_r:wpa_t 6836 ? S 0:00 sshd: kutulu@pts/0 |
11 |
|
12 |
What did you do to fix the transition to get to wpa_t? Was it the same |
13 |
as my other response? If starts/stops services based on network |
14 |
availability, you'd probably want a transition back to initrc_t |
15 |
(init_domtrans_script(wpa_t)). Thats assuming it uses the init scripts |
16 |
to control the services. |
17 |
|
18 |
-- |
19 |
Chris PeBenito |
20 |
<pebenito@g.o> |
21 |
Developer, |
22 |
Hardened Gentoo Linux |
23 |
|
24 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243 |
25 |
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243 |