Bug 803349

Summary: allocate extra space for node names
Product: Red Hat Enterprise Linux 6 Reporter: Ondrej Moriš <omoris>
Component: auditAssignee: Steve Grubb <sgrubb>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: medium    
Version: 6.2CC: dapospis
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: audit-2.2-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 14:29:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ondrej Moriš 2012-03-14 13:54:56 UTC 
Description of problem:

When a node name is a part of audit message and its length is bigger than usually (~80 characters) then auparse fails to parse the rest of message. This can lead even to 'hidden' audit events.

Version-Release number of selected component (if applicable):

audit-2.1.3-3.el6

How reproducible:

100%

Steps to Reproduce:

# cat >log<<-EOF
node=1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890 type=DAEMON_ACCEPT msg=audit(1320238076.308:8675): addr=10.16.66.107:52363 port=52363 res=success
EOF

# ausearch -if log
  
Actual results:

<no matches>

Expected results:

----
time->Wed Dec 31 22:40:02 1969
node=1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890 type=DAEMON_ACCEPT msg=audit(1320238076.308:8675): addr=10.16.66.107:52363 port=52363 res=success

Additional info:

This problem has been originally reported as [1] and immediately resolved with [2] raising node name limit from ~80 to ~340 characters.

[1] https://www.redhat.com/archives/linux-audit/2012-March/msg00005.html
[2] https://fedorahosted.org/audit/changeset/671
Comment 2 Steve Grubb 2012-03-14 20:36:26 UTC 
audit-2.2-2.el6 was built to fix this issue.
Comment 5 errata-xmlrpc 2012-06-20 14:29:31 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.

http://rhn.redhat.com/errata/RHBA-2012-0929.html