From: "Walt Powell" <wpowell9@columbus.rr.com>
To: linux-audit@redhat.com
Subject: Audit rules use of flags.
Date: Wed, 21 Feb 2007 21:48:33 -0500 [thread overview]
Message-ID: <000601c7562b$f2978ff0$6400a8c0@powerbox> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 690 bytes --]
Hello all:
I have a requirement to audit/log all failed attempts to access files. I entered the following line in audit.rules:
-w exit,always -S open -F success!=0
and audit flags all file exits regardless of success. When I try:
-w exit,possible -S open -F success!=0
it does NOT flag any file openings, including failure. I am curious if:
-w exit,never -S open -F success=0
but I suspect that the 'first hit takes it' nature of audit-1.0.12 will make the flag at the end useless.
So I suppose the question is - do I need to put the -F flag before the -w portion of the entry, or is there some other way to meet the requirement?
Thank you all for any insight.
[-- Attachment #1.2: Type: text/html, Size: 1845 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2007-02-22 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 2:48 Walt Powell [this message]
2007-02-22 14:06 ` Audit rules use of flags Steve Grubb
2007-02-26 16:04 ` 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='000601c7562b$f2978ff0$6400a8c0@powerbox' \
--to=wpowell9@columbus.rr.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