From: Linda Knippers <linda.knippers@hp.com>
To: lane.williams@jhuapl.edu
Cc: Linux-audit@redhat.com
Subject: Re: auditd/auditctl SLED10
Date: Thu, 20 Jul 2006 16:08:35 -0400 [thread overview]
Message-ID: <44BFE2C3.9050405@hp.com> (raw)
In-Reply-To: <1153424647.7866.11.camel@willipl1-ld1.jhuapl.edu>
There was a bug at one point where the '-F success=0' didn't
work but '-F success!=1' did work. You might want to try that
as a workaround. You might also try an strace on whatever program
you're using to test with to make sure there there isn't an access()
system call before the open. If there is, then you'll want to audit
access failures.
-- ljk
Lane Williams wrote:
> I am using audit 1.1.3 under SuSE Enterprise 10. I was wondering if
> anyone could give me an idea of how to log when someone tries to open a
> file which they do not have access to.
>
> I've tried the example
>
> auditctl -a exit,always -S open -F success=0
>
> When I do this I get nothing in the logs. But if I add the following
>
> auditctl -a entry,always -S open
>
> I get all of the entries and the open failures when there is "No such
> file or directory", but no access violations...
>
> Thanks for any help,
>
> Lane
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2006-07-20 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 14:08 auid bug Steve
2006-07-20 15:19 ` Linda Knippers
2006-07-20 19:44 ` auditd/auditctl SLED10 Lane Williams
2006-07-20 20:08 ` Linda Knippers [this message]
2006-07-21 12:14 ` Lane Williams
2006-07-21 14:31 ` Linda Knippers
2006-07-21 14:35 ` Marcus Meissner
2006-07-21 20:49 ` Lane Williams
2006-07-21 0:54 ` Klaus Weidner
2006-07-21 6:02 ` Marcus Meissner
2006-07-21 12:04 ` Lane Williams
2006-07-24 16:04 ` auid bug Steve
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=44BFE2C3.9050405@hp.com \
--to=linda.knippers@hp.com \
--cc=Linux-audit@redhat.com \
--cc=lane.williams@jhuapl.edu \
/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.