From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH bpf-next v8 05/11] seccomp,landlock: Enforce Landlock programs per process hierarchy Date: Tue, 27 Feb 2018 17:36:34 +0000 Message-ID: References: <20180227004121.3633-1-mic@digikod.net> <20180227004121.3633-6-mic@digikod.net> <20180227020856.teq4hobw3zwussu2@ast-mbp> <20180227045458.wjrbbsxf3po656du@ast-mbp> <20180227053255.a7ua24kjd6tvei2a@ast-mbp> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Casey Schaufler Cc: Andy Lutomirski , Alexei Starovoitov , =?UTF-8?B?TWlja2HDq2wgU2FsYcO8bg==?= , LKML , Alexei Starovoitov , Arnaldo Carvalho de Melo , Daniel Borkmann , David Drysdale , "David S . Miller" , "Eric W . Biederman" , Jann Horn , Jonathan Corbet , Michael Kerrisk , Kees Cook , Paul Moore , Sargun Dhillon , "Serge E . Hallyn" , Shuah Khan , Tejun Heo , Thomas Graf List-Id: linux-api@vger.kernel.org On Tue, Feb 27, 2018 at 5:30 PM, Casey Schaufler wrote: > On 2/27/2018 8:39 AM, Andy Lutomirski wrote: >> On Tue, Feb 27, 2018 at 5:32 AM, Alexei Starovoitov >> wrote: >>> [ Snip ] >> An earlier version of the patch set used the seccomp filter chain. >> Mickaƫl, what exactly was wrong with that approach other than that the >> seccomp() syscall was awkward for you to use? You could add a >> seccomp_add_landlock_rule() syscall if you needed to. >> >> As a side comment, why is this an LSM at all, let alone a non-stacking >> LSM? It would make a lot more sense to me to make Landlock depend on >> having LSMs configured in but to call the landlock hooks directly from >> the security_xyz() hooks. > > Please, no. It is my serious intention to have at least the > infrastructure blob management in within a release or two, and > I think that's all Landlock needs. The security_xyz() hooks are > sufficiently hackish as it is without unnecessarily adding more > special cases. > > What do you mean by "infrastructure blob management"?