From: Matthew Booth <mbooth@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Status of /etc/audit/filter.conf
Date: Mon, 23 Apr 2007 21:38:21 +0100 [thread overview]
Message-ID: <1177360701.6885.9.camel@localhost.localdomain> (raw)
In-Reply-To: <39d2723b0704231309m3f4aaa64tf5e58477f15c2198@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1349 bytes --]
On Mon, 2007-04-23 at 16:09 -0400, Aaron Lippold wrote:
> I have a security checking script that is complaining that my system
> is not able to audit all discretionary access to control permission
> modifications.
>
> To verify this it is looking for /etc/audit/filter.conf
>
> Is this still the correct place to look on RHEL4/5? I'd assume not
> since I can't find a man page on audit-filter.conf anymore.
filter.conf was a LAuS configuration file, which is no longer used.
Auditing in RHEL4 and RHEL 5 is entirely unrelated to LAuS. The
approximately corresponding information is in /etc/audit.rules (RHEL4)
or /etc/audit/audit.rules (RHEL5) iirc.
> If not, where and how would I add this feature to my audit configuration?
That really depends what 'discretionary access to control permission
modifications' actually means to the person who wrote it ;) I'm guessing
it refers to auditing the chmod family of system calls, in which case
you would add the following line to /etc/audit/audit.rules in RHEL 5:
-a entry,always -S chmod -S fchmod
and start the audit daemon. These calls will then be logged
in /var/log/audit.log.
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services
M: +44 (0)7977 267231
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-04-23 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 20:09 Status of /etc/audit/filter.conf Aaron Lippold
2007-04-23 20:38 ` Matthew Booth [this message]
2007-04-25 20:35 ` Bill Tangren
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=1177360701.6885.9.camel@localhost.localdomain \
--to=mbooth@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