public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Marcus Meissner <meissner@suse.de>
Cc: linux-audit@redhat.com
Subject: Re: Which userspace packages modified for audit
Date: Mon, 26 Feb 2007 09:40:13 -0500	[thread overview]
Message-ID: <200702260940.13903.sgrubb@redhat.com> (raw)
In-Reply-To: <20070226132109.GA3749@suse.de>

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

  reply	other threads:[~2007-02-26 14:40 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
2007-02-26 14:40             ` Steve Grubb [this message]
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=200702260940.13903.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=meissner@suse.de \
    /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