Mailinglist Archive: opensuse-bugs (4724 mails)

< Previous Next >
[Bug 582399] SELinux: init is not transitioning out of system_u/sysadm_t when init_upstart=0 boolean is set
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 6 Apr 2010 14:35:13 +0000
  • Message-id: <20100406143513.1D01B245520@xxxxxxxxxxxxxxxxxxxxxx>

--- Comment #8 from Justin mattock <justinmattock@xxxxxxxxx> 2010-04-06
14:35:11 UTC ---
with the chmod to the config, this fixed the issue where there was a dbus error
when gdm was starting(/etc/selinux/targeted no such file or directory).

With the above, on a fresh install,and SELinux(no file labeling), you can see
the error in /var/log/gdm/*)
keep in mind, one thing I noticed is as soon as you label the filesystem, this
error is not reported in /var/log/gdm/*(but the system still craps out with a
dbus error).

As for upstart... I'm wondering if it's time we have an in kernel function todo
so(one thing I learned with building my own system, is hunting down a patch for
sysvinit for SELinux, was a nightmare(could only imagine upstart).

a good example that comes to mind(keep in mind this is just an example)would be
something maybe like:
a small little __initcall early in the boot process
This way the policy is loaded, there is no need to deal with sysv/upstart,
and SELinux can go about it's merry way of loading and protecting.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >