All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amy Griffis <amy.griffis@hp.com>
To: "Timothy R. Chavez" <tinytim@us.ibm.com>
Cc: linux-audit@redhat.com
Subject: Re: issue with file watches on Suse 10.1 using latest 2.6.18-rc4 and audit 1.2.3
Date: Thu, 10 Aug 2006 11:40:41 -0400	[thread overview]
Message-ID: <20060810154041.GA12092@fc.hp.com> (raw)
In-Reply-To: <1155222269.15877.8.camel@localhost.localdomain>

Timothy R. Chavez wrote:  [Thu Aug 10 2006, 11:04:29AM EDT]
> On Wed, 2006-08-09 at 18:08 -0400, Rick Warner wrote:
> > Hello all,
> > 
> > I am trying to set up file watches for files such as /etc/passwd 
> > and /etc/shadow.  I am using Suse 10.1.  I have updated the kernel to a 
> > kernel.org 2.6.18-rc4 kernel, and have updated the audit userspace tools to 
> > version 1.2.3.  I can add filesystem watches with "auditctl -w /etc/passwd" 
> > successfully now.  Entries in the audit.log are created. 
> > 
> > The first problem is that when I use "aureport -w", it tells me "<no events of 
> > interest were found>".  Using "aureport -f" instead, it shows entries 
> > for /etc/passwd, but the auid column for all results is -1 (or "unset" if 
> > using the -i option to aureport).  Looking at the audit logfile, 
> > auid=4294967295 which then correlates to -1 when used as a signed vs unsigned 
> > int.
> > 
> > How can I fix this?
> > 
> 
> Rick,
> 
> I believe a special PAM package is used to capture the login uid (auid).
> I'm guessing that's where your problem lies.

pam_loginuid(8) has some helpful info.

      reply	other threads:[~2006-08-10 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 22:08 issue with file watches on Suse 10.1 using latest 2.6.18-rc4 and audit 1.2.3 Rick Warner
2006-08-10 15:04 ` Timothy R. Chavez
2006-08-10 15:40   ` Amy Griffis [this message]

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=20060810154041.GA12092@fc.hp.com \
    --to=amy.griffis@hp.com \
    --cc=linux-audit@redhat.com \
    --cc=tinytim@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.