<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Apparmor support in ConditionSecurity"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63312#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Apparmor support in ConditionSecurity"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63312">bug 63312</a>
from <span class="vcard"><a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> <span class="fn">Lennart Poettering</span></a>
</span></b>
<pre>Hmm, so, the current implementation of the SELinux check not only checks
whether SELinux is compiled into the kernel, but also if it is turned on during
runtime. I wonder if we should have the same for AppArmor? Is there a nice way
to check whether AppArmor is actually turned on?
(Also, as a side note, we currently load SELinux, IMA and SMACK policies from
early PID 1, so that they are applied before the first process is started. Do
we want the same for AppArmor?)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>