From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcus Meissner Subject: Re: Which userspace packages modified for audit Date: Mon, 26 Feb 2007 14:21:09 +0100 Message-ID: <20070226132109.GA3749@suse.de> References: <20070222230340.GA7527@suse.de> <200702251341.38443.sgrubb@redhat.com> <20070225184156.GA24540@suse.de> <200702251440.57522.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200702251440.57522.sgrubb@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Sun, Feb 25, 2007 at 02:40:57PM -0500, Steve Grubb wrote: > On Sunday 25 February 2007 13:41:56 Marcus Meissner wrote: > > Most of them have just support for emitting USER_LOGIN audit records. > > > > Are these necessary, because PAM emits USER_START / USER_END records > > anyway... > > 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? The pam_loginuid module could also generate the USER_LOGIN messages for instance? Ciao, Marcus