[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201501042050.EEH30201.FJVtFHMQOLSFOO@I-love.SAKURA.ne.jp>
Date: Sun, 4 Jan 2015 20:50:49 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: rgb@...hat.com
Cc: sgrubb@...hat.com, linux-security-module@...r.kernel.org,
linux-audit@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] TaskTracker : Simplified thread information tracker.
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?
--
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