From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753246AbdEDO7c (ORCPT ); Thu, 4 May 2017 10:59:32 -0400 Received: from h2.hallyn.com ([78.46.35.8]:60766 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751950AbdEDO6a (ORCPT ); Thu, 4 May 2017 10:58:30 -0400 Date: Thu, 4 May 2017 09:58:33 -0500 From: "Serge E. Hallyn" To: Djalal Harouni Cc: Andy Lutomirski , Kees Cook , Andy Lutomirski , Linux Kernel Mailing List , Andrew Morton , "Serge E. Hallyn" , "kernel-hardening@lists.openwall.com" , LSM List , Linux API , Dongsu Park , Casey Schaufler , James Morris , Paul Moore , Tetsuo Handa , Greg Kroah-Hartman , Jonathan Corbet , Jessica Yu , Rusty Russell , Arnaldo Carvalho de Melo , Mauro Carvalho Chehab , Ingo Molnar , belakhdar abdeldjalil , Peter Zijlstra , Linus Torvalds Subject: Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction Message-ID: <20170504145832.GA28002@mail.hallyn.com> References: <1492640420-27345-1-git-send-email-tixxdz@gmail.com> <1492640420-27345-3-git-send-email-tixxdz@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 04, 2017 at 03:07:49PM +0200, Djalal Harouni wrote: > On Sat, Apr 22, 2017 at 2:17 PM, Djalal Harouni wrote: > > On Sat, Apr 22, 2017 at 1:28 AM, Andy Lutomirski wrote: > [...] > >> > >> My point is that all of these need some way to handle configuration > >> and inheritance, and I don't think that a bunch of per-task prctls is > >> the right way. As just an example, saying that interactive users can > >> autoload modules but other users can't, or that certain systemd > >> services can, etc, might be nice. Linus already complained that he > >> (i.e. user "torvalds" or whatever) should be able to profile the > >> kernel but that other uids should not be able to. > > > > Neat, maybe this could already be achieved with this interface and > > systemd-logind, "ModulesAutoloadUsers=andy" in logind.conf where > > "andy" is the only logged-in user able to trigger and autoload kernel > > modules. However maybe we should not restrict too much other bits or > > functionality of the other users, please let me will follow up later > > on it. > > > >> I personally like my implicit_rights idea, and it might be interesting > >> to prototype it. > > > > Andy following on the idea of per user settings, I'm curious did you > manage to make some advance on how to store the user settings ? the > user database format is old and not extensible, there was cgmanager or (v2 is under very very early consideration, would love to stay in the loop as this is considered) > other libcgroup but for resources, and no simple thing for such > restrictions example: "RestrictLinuxModules=user" that will prevent > such users from making/loading extra Linux features/modules that are > not already available... > > Thanks! > > -- > tixxdz