[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.11.1504302119510.19912@namei.org>
Date: Thu, 30 Apr 2015 21:20:16 +1000 (AEST)
From: James Morris <jmorris@...ei.org>
To: John Johansen <john.johansen@...onical.com>
cc: Casey Schaufler <casey@...aufler-ca.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Kees Cook <kees@...flux.net>, Paul Moore <paul@...l-moore.com>,
LSM <linux-security-module@...r.kernel.org>,
James Morris <james.l.morris@...cle.com>,
linux-kernel@...r.kernel.org
Subject: Re: Module stacking next steps
On Wed, 29 Apr 2015, John Johansen wrote:
> On 04/29/2015 06:55 PM, James Morris wrote:
> > On Tue, 21 Apr 2015, Casey Schaufler wrote:
> >
> >>
> >> James, do you want to take the module stacking changes in through
> >> the security tree? Are there remaining objections or concerns? What
> >> procedure would you like to follow?
> >
> > What's the overall consensus on this -- do people generally see it as
> > useful and necessary, and is it ready to go in?
> >
> > Any objections or concerns?
> >
> No objections, and I know there are several people interested in seeing
> this land.
>
> I am happy with the code, and my only concerns lie with things that this
> explicitly doesn't support yet (ie. larger lsm stacking, secids, ...)
Ok, Casey, please send an updated final version for everyone to check.
--
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists