Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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-0526.html
Description of problem: Version-Release number of selected component (if applicable): dbus-1.2.24-3.el6.ppc64 dbus-devel-1.2.24-3.el6.ppc64 dbus-glib-0.86-5.el6.ppc64 dbus-libs-1.2.24-3.el6.ppc64 dbus-python-0.83.0-6.1.el6.ppc64 eggdbus-0.6-3.el6.ppc64 fprintd-0.1-19.git04fd09cfa.el6.ppc64 fprintd-pam-0.1-19.git04fd09cfa.el6.ppc64 selinux-policy-3.7.19-78.el6.noarch selinux-policy-doc-3.7.19-78.el6.noarch selinux-policy-minimum-3.7.19-78.el6.noarch selinux-policy-mls-3.7.19-78.el6.noarch selinux-policy-targeted-3.7.19-78.el6.noarch How reproducible: always Steps to Reproduce: 1) get a RHEL-6.1 machine with active MLS policy 2) log in as root via console 3) run following commands: # sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Mode from config file: enforcing Policy version: 24 Policy from config file: mls # id -Z root:sysadm_r:sysadm_t:SystemLow-SystemHigh # newrole -r secadm_r Password: # id -Z root:secadm_r:secadm_t:SystemLow-SystemHigh # exit logout # id -Z root:sysadm_r:sysadm_t:SystemLow-SystemHigh Actual results: ---- time->Thu Mar 10 15:52:57 2011 type=USER_AVC msg=audit(1299790377.360:197): user pid=1215 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s15:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_call interface=net.reactivated.Fprint.Manager member=GetDefaultDevice dest=net.reactivated.Fprint spid=3154 tpid=3156 scontext=root:sysadm_r:newrole_t:s0-s15:c0.c1023 tcontext=system_u:system_r:fprintd_t:s0-s15:c0.c1023 tclass=dbus : exe="/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?' ---- Expected results: no AVCs