[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87vb0bbzyo.fsf@x220.int.ebiederm.org>
Date: Mon, 11 Jul 2016 16:57:03 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Topi Miettinen <toiwoton@...il.com>
Cc: linux-kernel@...r.kernel.org, mladek@...e.com, luto@...nel.org,
serge@...lyn.com, keescook@...omium.org,
Paul Moore <paul@...l-moore.com>,
Eric Paris <eparis@...hat.com>, Tejun Heo <tj@...nel.org>,
Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Serge Hallyn <serge.hallyn@...onical.com>,
linux-audit@...hat.com (moderated list:AUDIT SUBSYSTEM),
cgroups@...r.kernel.org (open list:CONTROL GROUP (CGROUP)),
linux-security-module@...r.kernel.org (open list:CAPABILITIES)
Subject: Re: [PATCH] capabilities: audit capability use
Topi Miettinen <toiwoton@...il.com> writes:
> There are many basic ways to control processes, including capabilities,
> cgroups and resource limits. However, there are far fewer ways to find
> out useful values for the limits, except blind trial and error.
>
> Currently, there is no way to know which capabilities are actually used.
> Even the source code is only implicit, in-depth knowledge of each
> capability must be used when analyzing a program to judge which
> capabilities the program will exercise.
>
> Generate an audit message at system call exit, when capabilities are used.
> This can then be used to configure capability sets for services by a
> software developer, maintainer or system administrator.
>
> Test case demonstrating basic capability monitoring with the new
> message types 1330 and 1331 and how the cgroups are displayed (boot to
> rdshell):
You totally miss the interactions with the user namespace so this won't
give you the information you are aiming for.
Eric
Powered by blists - more mailing lists