Bug 731723 - Audit system updates for 6.2
Summary: Audit system updates for 6.2
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: audit
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Steve Grubb
QA Contact: Ondrej Moriš
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-18 13:32 UTC by Steve Grubb
Modified: 2011-12-06 18:20 UTC (History)
3 users (show)

Fixed In Version: audit-2.1.3-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Last Closed: 2011-12-06 18:20:20 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1739 normal SHIPPED_LIVE audit bug fix and enhancement update 2011-12-06 01:01:51 UTC

Description Steve Grubb 2011-08-18 13:32:21 UTC
Description of problem:
There are a number of items fixed in upstream audit code that would be beneficial to pull in. The following is a list of relevant changes:

- Fix parsing of EXECVE records to not escape argc field
- If auditd's disk is full, send the right reason to client (#715315)
- Update linker flags for better relro support
- Make default size of logs bigger (#727310)
- Disable 2 kerberos config options in audisp-remote.conf
- In auditd, cleanup DAEMON_ACCEPT and DAEMON_CLOSE addr fields
- In ausearch/report, parse addr field of DAEMON_ACCEPT & DAEMON_CLOSE records
- If auditd shutsdown due to failed tcp init, write a DAEMON_ABORT event
- Parse and interpret NETFILTER_PKT events correctly
- Return error if auditctl -l fails (#709345)
- When ausearch is interpretting, output "as is" if no = is found
- Fix autrace to use correct syscalls on s390 and s390x systems
- Correct autrace rule for 32 bits systems

Comment 7 errata-xmlrpc 2011-12-06 18:20:20 UTC
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.


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