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.
Description of problem:
authconfig-gtk generates avc when connecting to NIS domain
Version-Release number of selected component (if applicable):
authconfig-gtk-6.2.8-8.el7
How reproducible:
Steps to Reproduce:
1.run authconfig-gtk
2.try join to NIS domain
3.
Actual results:
several avc messages because nis_enabled selinux boolean is disabled
Expected results:
no avc
Additional info:
try join to existing and not existing NIS domain, both cases cause avc
This seems to be transient error only due to authconfig modifying the nsswitch.conf first and running the setsebool later. I do not want to change this now as the change would be too invasive.
Comment 4RHEL Program Management
2014-10-21 14:35:54 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
After more thinking about this I decided to reject the bug. It would require splitting the boolean toggling and the rest of actions done in the post() method and given this is only minor transient issue without a real customer impact I do not think we should try to spend resources on it.