From: Steve Grubb <sgrubb@redhat.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Possible typo in 22-ignore-chrony.rules
Date: Mon, 18 Jan 2021 08:45:13 -0500 [thread overview]
Message-ID: <5427786.DvuYhMxLoT@x2> (raw)
In-Reply-To: <1824339272.504544.1610944958091@mail.yahoo.com>
On Sunday, January 17, 2021 11:42:38 PM EST Joe Wulf wrote:
> This snippit in both rules in that file (for both v2.8.5 and v3.0.0) "-F
> auid=unset -Fuid=chrony" for the second "-F" seems to be missing a space
> after the "-F". Correct?
Yeah, it looks that way. Fixed. Thanks!
> IRT to the comment in this rule file, "These
> rules suppress the time-change event when chrony does time updates"; does
> that mean IF these two rules were not included or commented-out, that the
> chrony time updates would 'log' events in the audit log?
Yes.
> How do these rules 'work' to suppress chrony time updates from being
> logged?
The audit rules is a first match wins system. These rules are in a file with a
22 in the name which preceeds rules whose file name starts with 30. In 30-
stig.rules, we have a rule that asks for any use of adjtimex to be logged
which is the syscall chrony uses to update time. Since the rule in 22 has a
never action and it preceeds the one from the stig, it matches first and takes
the never action which is not to log it.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
parent reply other threads:[~2021-01-18 13:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1824339272.504544.1610944958091@mail.yahoo.com>]
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=5427786.DvuYhMxLoT@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