Red Hat Bugzilla – Bug 967240
FutureFeature: ausearch to checkpoint its output to only report new events on successive executions
Last modified: 2014-10-14 03:14:23 EDT
Description of problem:
In order to better support the centralisation of audit, we require the ausearch utility to be able to checkpoint it's output such that successive invocations of the tool only output new complete events.
This is a SOLVED problem with a patch provided to the auditd mailing list as per
From: Burn Alting <burn swtf dyndns org>
To: linux-audit redhat com
Subject: [PATCH] ausearch: Add checkpoint capability and have incomplete logs carry forward when processing multiple audit.log files
Date: Sat, 11 May 2013 15:59:34 +1000
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Applied in upstream commit 934.
Testing this can be done as follows:
1) ausearch --start today --checkpoint chk
2) ausearch --start today --checkpoint chk
3) ausearch --start today --checkpoint chk
4) auditctl -m test
5) ausearch --start today --checkpoint chk
6) ausearch --start today --checkpoint chk
You should see events on steps 1 & 5. None on 2, 3, & 6.
audit-2.3.7-1.el6 was built to resolve this problem.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.