From: Linda Knippers <linda.knippers@hp.com>
To: Alexander Viro <aviro@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Logging failed open() calls on /var/log/audit/audit.log
Date: Tue, 27 Jun 2006 18:16:37 -0400 [thread overview]
Message-ID: <44A1AE45.2020405@hp.com> (raw)
In-Reply-To: <20060627220323.GK4199@devserv.devel.redhat.com>
Alexander Viro wrote:
> On Tue, Jun 27, 2006 at 05:36:43PM -0400, Linda Knippers wrote:
>
>>Steve Grubb wrote:
>>
>>>On Tuesday 27 June 2006 17:15, Amy Griffis wrote:
>>>
>>>
>>>>If you would like to see a record in this case, you must add a watch
>>>>for /var/log/audit.
>>>
>>>
>>>I don't see a record watching this either.
>>
>>I think we're missing the directory lookup syscall(s) on watches
>>right now.
>
>
> Careful - that's one hell of a hot path. Note that we'll get many of
> those for each syscall that does pathname resolution; moreover, when
> we hit dcache, we should be careful about blocking.
Maybe its not actually the lookup we need. If I do this on RHEL4
I get an audit record for an open failure on /var/log/audit.
With the .34 lspp kernel and the 1.2.2 audit tools, I don't get
a record for a failed open, even though open seems to be registered
with the watch.
> [root@cert-e2 kernel]# /sbin/auditctl -l
> LIST_RULES: exit,always watch=/var/log/audit/audit.log (0x18) syscall=open,truncate,ftruncate,rename,mkdir,rmdir,creat,link,unlink,symlink,chmod,fchmod,chown,fchown,lchown
> LIST_RULES: exit,always watch=/var/log/audit (0xe) syscall=open,truncate,ftruncate,rename,mkdir,rmdir,creat,link,unlink,symlink,chmod,fchmod,chown,fchown,lchown
-- ljk
next prev parent reply other threads:[~2006-06-27 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 20:43 Logging failed open() calls on /var/log/audit/audit.log Robert Giles
2006-06-27 21:15 ` Amy Griffis
2006-06-27 21:21 ` Steve Grubb
2006-06-27 21:32 ` Timothy R. Chavez
2006-06-27 23:10 ` Amy Griffis
2006-06-27 21:32 ` Amy Griffis
2006-06-27 21:36 ` Linda Knippers
2006-06-27 22:03 ` Alexander Viro
2006-06-27 22:16 ` Linda Knippers [this message]
2006-06-29 16:34 ` Klaus Weidner
2006-06-29 18:04 ` LC Bruzenak
2006-06-29 18:12 ` Robert Giles
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=44A1AE45.2020405@hp.com \
--to=linda.knippers@hp.com \
--cc=aviro@redhat.com \
--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