On 09/04/2013 09:22 AM, Eric W. Biederman wrote:
Jan Kaluza writes:
Server-like processes in many cases need credentials and other
metadata of the peer, to decide if the calling process is allowed to
request a specific action, or the server just wants to log away this
type of information for a
On 09/04/2013 04:58 PM, Richard Guy Briggs wrote:
On Wed, Sep 04, 2013 at 12:42:26AM -0700, Eric W. Biederman wrote:
Jan Kaluza writes:
Hi,
this patchset against net-next (applies also to linux-next) adds 3 new types
of "Socket"-level control message (SCM_AUDIT, SCM_PROCINFO and SCM_CGROUP).
On 09/04/2013 05:30 PM, Eric Dumazet wrote:
On Wed, 2013-09-04 at 11:20 -0400, Richard Guy Briggs wrote:
On Wed, Sep 04, 2013 at 10:58:30AM -0400, Richard Guy Briggs wrote:
On Wed, Sep 04, 2013 at 12:42:26AM -0700, Eric W. Biederman wrote:
Jan Kaluza writes:
this patchset against net-next (a
On 01/13/2014 08:44 PM, Casey Schaufler wrote:
On 1/13/2014 12:01 AM, Jan Kaluza wrote:
Hi,
this patchset against net-next (applies also to linux-next) adds 3 new types
of "Socket"-level control message (SCM_AUDIT, SCM_PROCINFO and SCM_CGROUP).
How about the group list, while you're at it?
On 01/16/2014 12:23 AM, Tejun Heo wrote:
On Wed, Jan 15, 2014 at 06:21:43PM -0500, Eric Paris wrote:
Reliably being able to audit what process requested an action is
extremely useful. And I like the audit patch, as it is a couple of ints
we are storing.
procinfo and cgroup can both be up to 4k
5 matches
Mail list logo
