Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: "Boyce, Kevin P [US] (AS)" <Kevin.Boyce@ngc.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Exclude Watched Items
Date: Mon, 15 May 2017 23:22:38 -0400	[thread overview]
Message-ID: <20170516032238.GP21241@madcap2.tricolour.ca> (raw)
In-Reply-To: <3a9b11a79cc643ebb56c841a38b29846@XCGVAG30.northgrum.com>

On 2017-05-15 21:08, Boyce, Kevin P [US] (AS) wrote:
> Ok I admit I should know how to do this, but it is evident I do not.
> 
> On RHEL 5.11, what is the correct way for me to not audit anything in /proc?
> 
> I had tried:
> -d entry,always -S all -F dir=/proc
> -a exclude,always -F dir=/proc
> 
> Both of these are ignored.  The first makes sense because I guess -d
> must match exactly a rule already loaded in the kernel.

"-d" says delete the rule.  (I think the entry list is deprecated.)

> The second is telling me I have an invalid message type, but I can't
> seem to find the valid message types documented in the man pages.

The exclude list only supports "-F msgtype=" on anything that old.

More types are supported upstream and only very recent RHEL7.

> Other systemcalls which are audited are open, fopen, chown, chattr, etc.
> I am trying to prevent auditing of the open syscall on /proc/...
> because there are a lot of them, and it is not a requirement.

How about "-a exit,never -F dir=/proc"?

> Kevin

- RGB

--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635

  reply	other threads:[~2017-05-16  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 21:08 Exclude Watched Items Boyce, Kevin P [US] (AS)
2017-05-16  3:22 ` Richard Guy Briggs [this message]
2017-05-16 12:54   ` EXT :Re: " Boyce, Kevin P [US] (AS)
2017-05-16 21:17     ` 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=20170516032238.GP21241@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=Kevin.Boyce@ngc.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