RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1622045 - semanage_seuser_audit() does not log username in AUDIT_ROLE_REMOVE messages
Summary: semanage_seuser_audit() does not log username in AUDIT_ROLE_REMOVE messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libsemanage
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Vit Mojzis
QA Contact: Jan Zarsky
URL:
Whiteboard:
Depends On:
Blocks: 1256920 1294663 1624764
TreeView+ depends on / blocked
 
Reported: 2018-08-24 09:19 UTC by Jan Zarsky
Modified: 2018-10-30 09:36 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1629614 (view as bug list)
Environment:
Last Closed: 2018-10-30 09:35:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3088 0 None None None 2018-10-30 09:36:06 UTC

Description Jan Zarsky 2018-08-24 09:19:44 UTC
Description of problem:
Function semanage_seuser_audit() is used for logging AUDIT_ROLE_ASSIGN and AUDIT_ROLE_REMOVE messages. These messages should contain the 'acct' field with username. When removing login records, the 'acct' field is not logged.

Version-Release number of selected component (if applicable):
libsemanage-2.5-13.el7.x86_64
policycoreutils-2.5-25.el7.x86_64 (needed for reproducer)

How reproducible:
always

Steps to Reproduce:
# useradd testuser
# semanage login -a -s staff_u testuser
# semanage login -d testuser
# ausearch -m role_remove -ts recent
----
time->Fri Aug 24 05:14:19 2018
type=ROLE_REMOVE msg=audit(1535102059.183:309): pid=10121 uid=0 auid=0 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=login id=0 old-seuser=staff_u old-role=staff_r,sysadm_r,system_r,unconfined_r old-range=s0-s0:c0.c1023 new-seuser=? new-role=? new-range=? exe="/usr/bin/python2.7" hostname=? addr=? terminal=pts/0 res=success'

Actual results:
no acct field

Expected results:
acct field with value 'testuser'

Additional info:
This bug was discovered when working on https://bugzilla.redhat.com/show_bug.cgi?id=1294663

Comment 9 errata-xmlrpc 2018-10-30 09:35:42 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.

https://access.redhat.com/errata/RHBA-2018:3088


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