Bug 174392

Summary: incorrect audit record in userdel
Product: Red Hat Enterprise Linux 4 Reporter: Linda Knippers <linda.knippers>
Component: shadow-utilsAssignee: Peter Vrabec <pvrabec>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: andriusb, poelstra, sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2006-0035 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-07 18:29:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 168429    
Description Flags
patch to fix incorrect audit record none

Description Linda Knippers 2005-11-28 19:14:49 UTC
Description of problem:
The audit record emitted from userdel when a user's mail file is removed 
incorrectly says the operation failed even when it succeeded.

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

How reproducible:

Steps to Reproduce:
1.  Make sure auditd is running
2.  Create a user account with useradd
3.  Delete the account with 'userdel -r'
Actual results:
type=USER_CHAUTHTOK msg=audit(1132783148.877:449): user pid=18753 uid=0 auid=501
msg='userdel: op=deleting mail file acct=ljk2 res=failed'

Expected results:
Should say "res=success"

Additional info:
A one line fix (attached) is needed in userdel.c

We need a version of shadow-utils with this fix so that HP can complete its CAPP
evaluation of RHEL4 U2.

Comment 1 Linda Knippers 2005-11-28 19:14:50 UTC
Created attachment 121557 [details]
patch to fix incorrect audit record

Comment 3 Peter Vrabec 2005-11-29 11:09:42 UTC
rawhide fixed.

Comment 7 Red Hat Bugzilla 2006-03-07 18:29:42 UTC
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 the 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.