From: Marcus Meissner <meissner@suse.de>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Which userspace packages modified for audit
Date: Mon, 26 Feb 2007 14:21:09 +0100 [thread overview]
Message-ID: <20070226132109.GA3749@suse.de> (raw)
In-Reply-To: <200702251440.57522.sgrubb@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
next prev parent reply other threads:[~2007-02-26 13:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 23:03 Which userspace packages modified for audit Tony Jones
2007-02-23 10:18 ` SUSE ELS and Audit Johnston Mark (UK)
2007-02-23 10:20 ` Marcus Meissner
2007-02-23 10:26 ` Roman Drahtmueller
2007-02-23 10:59 ` Johnston Mark (UK)
2007-02-23 11:47 ` Which userspace packages modified for audit Steve Grubb
2007-02-23 14:22 ` Matthew Booth
2007-02-25 18:41 ` Steve Grubb
2007-02-25 18:41 ` Marcus Meissner
2007-02-25 19:40 ` Steve Grubb
2007-02-26 13:21 ` Marcus Meissner [this message]
2007-02-26 14:40 ` Steve Grubb
2007-02-25 22:15 ` Matthew Booth
2007-02-25 22:30 ` Steve Grubb
2007-02-25 22:35 ` Matthew Booth
2007-02-25 23:07 ` Steve Grubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070226132109.GA3749@suse.de \
--to=meissner@suse.de \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox