This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 529851 - audit package upgrade for RHEL5.5
audit package upgrade for RHEL5.5
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: audit (Show other bugs)
All Linux
high Severity medium
: rc
: ---
Assigned To: Steve Grubb
BaseOS QE Security Team
: Rebase
Depends On:
Blocks: 5.5TechNotes-Updates
  Show dependency treegraph
Reported: 2009-10-20 09:14 EDT by Steve Grubb
Modified: 2010-11-22 18:27 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-03-30 04:20:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steve Grubb 2009-10-20 09:14:08 EDT
Description of problem:
The audit package should be rebased in the 5.5 release cycle to the 1.7.16 release. The current change log is here:

Since 1.7.13 (RHEL5.4) some of the highlights are:

* Allow ausearch/report to specify multiple node names (needed for remote logging)
* Make auparse handle empty AUSOURCE_FILE_ARRAY correctly (was segfaulting)
* In auditctl rules allow a0-a3 to be negative numbers
* Add audit.rules man page
* In auditd reset syslog warnings if disk space becomes available
* Correct checking of != operator in audit_rule_fieldpair_data
* and many remote logging code improvements

Version-Release number of selected component (if applicable):
Comment 4 Steve Grubb 2009-12-08 16:12:00 EST
audit-1.7.17-1 was built to resolve this issue.
Comment 8 errata-xmlrpc 2010-03-30 04:20:03 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.