From: Steve Grubb <sgrubb@redhat.com>
To: "Boyce, Kevin P (AS)" <Kevin.Boyce@ngc.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: EXT :Re: audit.rules setting
Date: Tue, 22 Mar 2016 10:40:42 -0400 [thread overview]
Message-ID: <2807952.R0hKEWZBSv@x2> (raw)
In-Reply-To: <d2872ae671d74c08bc3457672f69c9fe@XCGVAG30.northgrum.com>
On Tuesday, March 22, 2016 02:26:33 PM Boyce, Kevin P wrote:
> With regard to this subject I don't know if it is possible, but it bothers
> me when shutting down a system that you get errors (when -e 2 is enabled)
> when auditd is stopping. That might be unavoidable though.
If this is a sysVinit system, then there are variables in /etc/sysconfig/auditd
such as AUDITD_CLEAN_STOP that determine what the init script does.
If you have a systemd based init system, then by default it does not modify
rules like the sysVinit one does. It does have a ExecStopPost= variable that
can be modified if you wanted to clear rules on shutdown.
-Steve
> -----Original Message-----
> From: linux-audit-bounces@redhat.com [mailto:linux-audit-bounces@redhat.com]
> On Behalf Of Steve Grubb Sent: Tuesday, March 22, 2016 10:06 AM
> To: linux-audit@redhat.com
> Subject: EXT :Re: audit.rules setting
>
> On Tuesday, March 22, 2016 12:55:25 PM Warron S French wrote:
> > Does the "-e 2" have to be the last line of the audit.rules file?
>
> Yes. Once its sent to the kernel, the kernel rules tables are immutable.
>
> > Does it have to be listed prior to all of the syscalls and watches
> > configured in the file?
>
> No. This will make it not load anything.
>
> -Steve
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2016-03-22 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 12:55 audit.rules setting Warron S French
2016-03-22 14:06 ` Steve Grubb
2016-03-22 14:26 ` EXT :Re: " Boyce, Kevin P (AS)
2016-03-22 14:40 ` 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=2807952.R0hKEWZBSv@x2 \
--to=sgrubb@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