Re: [PATCH v10] LSM: Multiple concurrent LSMs

[Casey Schaufler <casey@schaufler-ca.com>]

On 12/12/2012 12:51 PM, Eric Paris wrote:
> On Wed, Dec 12, 2012 at 3:46 PM, Casey Schaufler <casey@schaufler-ca.com> wrote:
>
>> You want loading SELinux policy to fail in this case, because
>> you know that the system isn't going to work properly. You are
>> suggesting a kernel change that inhibits loading the SELinux
>> policy unless userspace tells the kernel it is OK to do so
>> if present is not selinux.
> Now you get me.  I just don't understand why all LSMs wouldn't want
> this.  If they know they will fail, they should fail early and cleanly
> rather than unpredictably later.  If you LSM can't fail due to attr
> issues, this doesn't apply.
>
Ah. Any LSM see it, but each LSM is going to have to decide
what it does about it. SELinux can refuse to load policy.
Smack is perfectly happy to run without any rules set. There
is no major configuration event to fail.

Smack will be aggressively updating userspace. Smack does not
(alas) have the install base that SELinux enjoys. I am not
especially concerned for Smack, while I understand fully the
SELinux concern.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.