[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170530162550.19ba1811@alans-desktop>
Date: Tue, 30 May 2017 16:25:50 +0100
From: Alan Cox <gnomes@...rguk.ukuu.org.uk>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: jmorris@...ei.org, keescook@...omium.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-hardening@...ts.openwall.com, casey@...aufler-ca.com,
hch@...radead.org, igor.stoppa@...wei.com, james.l.morris@...cle.com,
paul@...l-moore.com, sds@...ho.nsa.gov
Subject: Re: [PATCH] LSM: Convert security_hook_heads into explicit array of
struct list_head
On Tue, 30 May 2017 23:29:10 +0900
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> wrote:
> James Morris wrote:
> > On Sun, 28 May 2017, Tetsuo Handa wrote:
> >
> > > can afford enabling". And we know that we cannot merge all security modules
> > > into mainline. Thus, allowing LKM-based LSM modules is inevitable.
> >
> > Nope, it's not inevitable. The LSM API only caters to in-tree users.
> >
> > I'm not sure why you persist against this.
>
> Then, we are willing to accept LSM modules with users less than 10, aren't we?
Why not if they are properly written and maintained. Historically we've
supported an entire architecture that had one machine ever built. We
supported a strange subclass of x86 machines for many years because James
Bottomley cared enough to do the work. We still support M68K, PA-RISC and
other stuff as well as plenty of hardware which probably has few users -
providing it doesn't cause maintenance problems.
Alan
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
