[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150119152550.GR29998@madcap2.tricolour.ca>
Date: Mon, 19 Jan 2015 10:25:50 -0500
From: Richard Guy Briggs <rgb@...hat.com>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-audit@...hat.com
Subject: Re: [PATCH] TaskTracker : Simplified thread information tracker.
On 15/01/04, Tetsuo Handa wrote:
> Hello.
>
> Richard Guy Briggs wrote:
> > > Richard Guy Briggs wrote:
> > > > On 14/09/28, Tetsuo Handa wrote:
> > > > > (Q2) Does auxiliary record work with only type=SYSCALL case?
> > > >
> > > > Auxiliary records don't work with AUDIT_LOGIN because that record has a
> > > > NULL context. Similarly for core dumps (AUDIT_ANOM_ABEND), AUDIT_SECCOMP,
> > > > configuration changes (AUDIT_CONFIG_CHANGE, AUDIT_FEATURE_CHANGE), most
> > > > (all?) AUDIT_USER_* messages.
> > > >
> > > I see, thank you.
> > >
> > > Although I feel that, from the point of view of troubleshooting, emitting
> > > history of thread's comm name into NULL-context records would help sysadmin
> > > to map login session and operations a user did from that login session,
> > > I'm OK with starting history of thread's comm name as auxiliary records
> > > (i.e. not emitted into NULL-context records).
> > >
> > > Adding LKML for reviewers. What else can I do for merging this patch?
> >
> > I'm willing to take it with some reflection and no significant
> > objections, in particular from userspace audit. I'll have a closer look
> > at it.
>
> Any comments on this patch?
It also occurs to me that the pid_t of that process in init PID
namespace would be useful for each entry.
- RGB
--
Richard Guy Briggs <rbriggs@...hat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists