On Thu, May 04, 2017 at 03:07:49PM +0200, Djalal Harouni wrote: > On Sat, Apr 22, 2017 at 2:17 PM, Djalal Harouni <tixxdz@xxxxxxxxx> wrote: > > On Sat, Apr 22, 2017 at 1:28 AM, Andy Lutomirski <luto@xxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
