Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: adding rules after setting rules immutable
Date: Thu, 08 Sep 2016 09:52:32 -0400	[thread overview]
Message-ID: <1606226.BHdsqEiX8T@x2> (raw)
In-Reply-To: <CAJdJdQ=xVMoN_s+03vkYJKbqVGF_mzZ+6BnbgrOM2bXDp12VAQ@mail.gmail.com>

On Thursday, September 8, 2016 9:42:09 AM EDT warron.french wrote:
> While working with RHEL-6 and RHEL-7 systems, and understanding that you
> can set rules to immutable by adding *-e 2* to the end of the audit.rules
> file(s)  I realized something.
> 
> If I want to add rules to a system due to new IT Governance, I might have
> to reboot every machine that gets the newly added rules.

Yes, you need to reboot. This is what immutable means - no changes allowed 
during runtime.


> Is this true, or can I get away with simply executing, on both versions of
> RHEL (6 and 7):
> augenrules --check
> augenrules --load

These will fail.


> I ask, because I want to write some puppet code that is smart enough to
> ensure the rules are put into place.  Do I really have to reboot a server
> in the middle of a work day or can I work around it with the use of the
> *augenrules* commands as listed above?

This is what immutable does. If you need flexibility to change rules at will, 
then you should comment out or delete the -e 2 at the end.

-Steve

  reply	other threads:[~2016-09-08 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 13:42 adding rules after setting rules immutable warron.french
2016-09-08 13:52 ` Steve Grubb [this message]
2016-09-08 16:16   ` Richard Guy Briggs

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=1606226.BHdsqEiX8T@x2 \
    --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