Red Hat Bugzilla – Full Text Bug Listing
|Summary:||pam USER_ROLE_CHANGE audit events missing some info|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Steve Grubb <sgrubb>|
|Component:||pam||Assignee:||Tomas Mraz <tmraz>|
|Status:||CLOSED ERRATA||QA Contact:||Milos Malik <mmalik>|
|Version:||6.0||CC:||mitr, mmalik, syeghiay|
|Fixed In Version:||pam-1.1.1-7.el6||Doc Type:||Bug Fix|
The audit records provided by the pam_selinux and pam_tally2 modules have been improved to include tty and remote hostname information in each recorded event.
|Last Closed:||2011-05-19 10:02:40 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
|Bug Blocks:||584498, 846801, 846802|
Description Steve Grubb 2011-02-15 09:23:12 EST
Description of problem: The USER_ROLE_CHANGE audit events are missing hostname, addr, and terminal fields. Looking at the code I see this: audit_log_user_message(audit_fd, AUDIT_USER_ROLE_CHANGE, msg, NULL, NULL, NULL, success) Those NULLs should be filled in with results from pam_get_item(). Steps to Reproduce: 1. Log in via sshd 2. As root user, ausearch --start today -m USER_ROLE_CHANGE
Comment 6 Tomas Mraz 2011-02-21 05:08:12 EST
There is no reasonable way how to get the remote host name in the separate executables. The faillock will be called by admin in an existing login session so it can be easily traced back. The unix_chkpwd audit was added for the case of screensaver password entry auditing - here this is also running in an existing login session.
Comment 10 Laura Bailey 2011-05-06 02:59:14 EDT
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The audit records provided by the pam_selinux and pam_tally2 modules have been improved to include tty and remote hostname information in each recorded event.
Comment 11 errata-xmlrpc 2011-05-19 10:02:40 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. http://rhn.redhat.com/errata/RHBA-2011-0685.html