[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jL8ijV8AXLeeakvP7iXeYGSgyVWOUw+Mp_M0oxL7jf0ZA@mail.gmail.com>
Date: Mon, 8 Apr 2019 08:02:51 -0700
From: Kees Cook <keescook@...omium.org>
To: David Rheinsberg <david.rheinsberg@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
John Johansen <john.johansen@...onical.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
linux-security-module <linux-security-module@...r.kernel.org>,
Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [REGRESSION] AppArmor module parameter layout changed with c5459b829b716
On Mon, Apr 8, 2019 at 12:21 AM David Rheinsberg
<david.rheinsberg@...il.com> wrote:
>
> Hi
>
> A recent commit changed how `/sys/module/apparmor/parameters/enabled`
> looks. It was "Y"/"N" before, now it is an integer. I *think* the
> commit that changed this was:
Oooh... the _output_ appears differently based on the type. Argh. Let
me work something up...
> commit c5459b829b716dafd226ad270f25c9a3050f7586
> Author: Kees Cook <keescook@...omium.org>
> Date: Thu Sep 13 22:28:48 2018 -0700
>
> LSM: Plumb visibility into optional "enabled" state
>
> I haven't recompiled with a revert, but changing the module-parameter
> type looks like the obvious culprit. I don't see how this change can
> be safe?
>
> This breaks the AppArmor detection of `dbus-broker`. Can the commit be reverted?
Thanks for catching this!
--
Kees Cook
Powered by blists - more mailing lists