public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Matthew Booth <mbooth@redhat.com>
To: linux-audit <linux-audit@redhat.com>
Subject: Prettier formatting of audit.rules
Date: Wed, 21 Feb 2007 11:23:25 +0000	[thread overview]
Message-ID: <1172057005.3970.26.camel@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1202 bytes --]

I note from the auditctl man page that sending a shorter list of audit
rules to the kernel is preferrable. Specifically, specifying lots of
system calls in a single rule is recommended. However, this makes
audit.rules unpleasant to look at and impossible to comment. While
audit.rules allows comments to be put on their own lines, it doesn't
allow a rule to be split over multiple lines, or comments at the end of
lines.

So rather than:

-a entry,always -S chmod -S fchmod -S chown -S fchown -S lchown -S creat
-S truncate -S ftruncate -S mkdir -S rmdir -S exit -S exit_group -S
execve -S vfork -S fork -S clone -F auid!= 101 -F auid!=102 -F auid!=103

it would be much nicer to write something like:

-a entry,always
    -S chmod -S fchmod
    -S chown -S fchown -S lchown # Attribute changes
    -S creat
    -S truncate -S ftruncate
    -S mkdir -S rmdir
    -S exit -S exit_group
    -S execve
    -S vfork -S fork -S clone # Task creation
    -F auid!= 101 -F auid!=102 -F auid!=103 # Filter Oracle activity

Matt
-- 
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 --]



             reply	other threads:[~2007-02-21 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 11:23 Matthew Booth [this message]
2007-02-21 18:45 ` Prettier formatting of audit.rules 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=1172057005.3970.26.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