[DSE-Dev] Bug#678564: Bug#678564: selinux-policy-default: Several process are running in incorrect context when using systemd

[Russell Coker]

On Sun, 2 Dec 2012, ayaka <randylxr at gmail.com> wrote:
> Package: selinux-policy-default
> Version: 2:2.20110726-11
> 
>    The context of /lib/systemd/systemd is
> system_u:object_r:lib_t:SystemLow,   but I think the correct is
> system_u:object_r:init_exec_t:SystemLow

Correct.  "restorecon -v /lib/systemd/systemd" should correct that.  I don't 
know why it would have got the wrong context unless you installed systemd 
while running a version of the policy that was considerably earlier than -11.

> The context of /usr/sbin/gdm3 is
> system_u:object_r:bin_t:SystemLow, but I think the correct is
> system_u:object_r:xdm_exec_t:SystemLow

If the xserver.pp module was loaded before gdm was installed then it should 
have had the correct context.  A restorecon operation should fix it if xserver 
is loaded.

>    I chconed they
>    Althought the /usr/bin/dbus-daemon is
> system_u:object_r:dbusd_exec_t:SystemLow, /usr/bin/X11/dbus-daemon is
> system_u:object_r:dbusd_exec_t:SystemLow But in ps axZ
>    system_u:system_r:init_t:s0      2182 ?        Ssl    0:01
>    /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile
>    --systemd-activation
>    user_u:user_r:user_dbusd_t:s0    4135 ?        Ssl    0:00
>    /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
>    user_u:user_r:user_dbusd_t:s0    4145 ?        Ssl    0:00
>    /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
>    Is the context of the first processe correct?

Strange.  But let's fix the gdm and systemd problems first.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/