Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Mackanick,
	Jason W CTR DISA GIG-OP" <jason.mackanick.ctr@disa.mil>,
	Valdis.Kletnieks@vt.edu
Subject: Re: Login/Logouts (UNCLASSIFIED)
Date: Wed, 28 Feb 2007 17:54:28 -0500	[thread overview]
Message-ID: <200702281754.28780.sgrubb@redhat.com> (raw)
In-Reply-To: <C20B7106.968%paul.whitney@mac.com>

On Wednesday 28 February 2007 17:48, Paul Whitney wrote:
> So does that mean this call audit would not work:
>
> -a exit,possible -w /bin/login -F success=0 -F success!=0

This would not audit anything for 3 reasons. "possible" tells it to collect 
the information in case its needed later. The -F options form an "and" 
condition. Both cannot be true at the same time. And "-w" is watches 
while "-a" is syscall auditing...you cannot mix the two.

You might try:

-w /bin/login -p x

But that would get you the fact that the file was executed but probably not 
the results of execution. (It probably should).

> What would be an entry to trap users successfully logging in?

We've patched the source code to entry points to send specific messages saying 
the intent of the pam session.

-Steve

  reply	other threads:[~2007-02-28 22:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 20:31 Login/Logouts (UNCLASSIFIED) Mackanick, Jason W CTR DISA GIG-OP
2007-02-28 21:13 ` Steve Grubb
2007-02-28 21:18 ` Valdis.Kletnieks
2007-02-28 22:48   ` Paul Whitney
2007-02-28 22:54     ` Steve Grubb [this message]
2007-03-01 13:41       ` Mackanick, Jason W CTR DISA GIG-OP
2007-03-01 14:05         ` Steve Grubb
2007-03-01 14:21           ` Mackanick, Jason W CTR DISA GIG-OP

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=200702281754.28780.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jason.mackanick.ctr@disa.mil \
    --cc=linux-audit@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