From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Which userspace packages modified for audit Date: Mon, 26 Feb 2007 09:40:13 -0500 Message-ID: <200702260940.13903.sgrubb@redhat.com> References: <20070222230340.GA7527@suse.de> <200702251440.57522.sgrubb@redhat.com> <20070226132109.GA3749@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070226132109.GA3749@suse.de> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Marcus Meissner Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Monday 26 February 2007 08:21, Marcus Meissner wrote: > > Yes. NISPOM is concerned about tracking login/logout. How do you > > distinguish an actual login/logout vs the start of a session with the pam > > records? su and cron, for example, do not do an actual login yet they > > create those records. > > We could really handle this together with the loginuid tracking, right? No, cron sets the loginuid because the action performed by the scripts is on a certain user's behalf. Everything is the way it is for a reason. -Steve