From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932468AbcINSdl (ORCPT ); Wed, 14 Sep 2016 14:33:41 -0400 Received: from mail-yb0-f182.google.com ([209.85.213.182]:35581 "EHLO mail-yb0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753801AbcINSdj (ORCPT ); Wed, 14 Sep 2016 14:33:39 -0400 MIME-Version: 1.0 In-Reply-To: <20160914072415.26021-19-mic@digikod.net> References: <20160914072415.26021-1-mic@digikod.net> <20160914072415.26021-19-mic@digikod.net> From: Andy Lutomirski Date: Wed, 14 Sep 2016 11:27:48 -0700 Message-ID: Subject: Re: [RFC v3 18/22] cgroup,landlock: Add CGRP_NO_NEW_PRIVS to handle unprivileged hooks To: =?UTF-8?B?TWlja2HDq2wgU2FsYcO8bg==?= Cc: "linux-kernel@vger.kernel.org" , Alexei Starovoitov , Arnd Bergmann , Casey Schaufler , Daniel Borkmann , Daniel Mack , David Drysdale , "David S . Miller" , Elena Reshetova , "Eric W . Biederman" , James Morris , Kees Cook , Paul Moore , Sargun Dhillon , "Serge E . Hallyn" , Tejun Heo , Will Drewry , "kernel-hardening@lists.openwall.com" , Linux API , LSM List , Network Development , "open list:CONTROL GROUP (CGROUP)" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id u8EIXj4J032532 On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote: > Add a new flag CGRP_NO_NEW_PRIVS for each cgroup. This flag is initially > set for all cgroup except the root. The flag is clear when a new process > without the no_new_privs flags is attached to the cgroup. > > If a cgroup is landlocked, then any new attempt, from an unprivileged > process, to attach a process without no_new_privs to this cgroup will > be denied. Until and unless everyone can agree on a way to properly namespace, delegate, etc cgroups, I think that trying to add unprivileged semantics to cgroups is nuts. Given the big thread about cgroup v2, no-internal-tasks, etc, I just don't see how this approach can be viable. Can we try to make landlock work completely independently of cgroups so that it doesn't get stuck and so that programs can use it without worrying about cgroup v1 vs v2, interactions with cgroup managers, cgroup managers that (supposedly?) will start migrating processes around piecemeal and almost certainly blowing up landlock in the process, etc? I have no problem with looking at prototypes for how landlock + cgroups would work, but I can't imagine the result being mergeable.