From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: the meaning of this audit entry
Date: Tue, 20 Nov 2007 21:27:18 -0500 [thread overview]
Message-ID: <200711202127.18447.sgrubb@redhat.com> (raw)
In-Reply-To: <1763.10.1.5.75.1195571288.squirrel@aa.usno.navy.mil>
On Tuesday 20 November 2007 10:08:08 am Bill Tangren wrote:
> Well, I'm just finding that out. Obviously I have to rewrite all my rules,
> or most of them, anyway. I'd like to blame someone else for the rules,
> since I was given these and told to use them, but I should know better.
> Obviously I have a lot to learn. I wish there was a tutorial or something
> I could read. I've gone over the man page, but I'm not learning enough
> from it.
Take a look at the capp.rules or nispom.rules file in the audit package. Those
are real working rules that have been commented. That is where I would start
if I were setting up a system.
> I'll star by splitting up the auid= rules, and observe what shows up in
> the logs.
I think your issues are more fundamental than that. I think you have more
rules than you shared with us and they are looking for unsuccessful calls and
not considering the exit codes. There are plenty of people on this mail list
that could help you with your rules if you told us what kinds of things you
were needing to audit.
-Steve
prev parent reply other threads:[~2007-11-21 2:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 21:22 the meaning of this audit entry Bill Tangren
2007-11-19 22:06 ` Steve Grubb
2007-11-20 15:36 ` Bill Tangren
2007-11-21 0:49 ` Mike Nixon
2007-11-21 2:17 ` Steve Grubb
2007-11-21 2:22 ` Steve Grubb
2007-11-19 22:13 ` Matthew Booth
2007-11-20 15:08 ` Bill Tangren
2007-11-21 2:27 ` Steve Grubb [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=200711202127.18447.sgrubb@redhat.com \
--to=sgrubb@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