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.
DescriptionNikolai Kondrashov
2012-11-13 14:56:31 UTC
Created attachment 644161[details]
Patch fixing the problem
Description of problem:
sudoRunAsUser #uid values match users neither with LDAP nor with SSSD backends
Version-Release number of selected component (if applicable):
sudo-1.8.6p3-5.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Use the attached LDIF file to fill a LDAP directory.
2. Use the attached sssd.conf as the base for SSSD configuration.
3. Execute the attached sudo_runas_spec_test with "ldap" or "sssd" argument depending on the configured backend.
Actual results:
sudoRunAsUser: user2: ALLOWED
sudoRunAsUser: user1: DENIED
sudoRunAsUser: #10002: DENIED
sudoRunAsUser: #10001: DENIED
sudoRunAsUser: %group_user2: ALLOWED
sudoRunAsUser: %group_user1: DENIED
sudoRunAsUser: +netgroup_user2: ALLOWED
sudoRunAsUser: +netgroup_user1: DENIED
sudoRunAsGroup: group_user2: ALLOWED
sudoRunAsGroup: group_user1: DENIED
sudoRunAsGroup: #20002: ALLOWED
sudoRunAsGroup: #20001: DENIED
(note the third line)
Expected results:
sudoRunAsUser: user2: ALLOWED
sudoRunAsUser: user1: DENIED
sudoRunAsUser: #10002: ALLOWED
sudoRunAsUser: #10001: DENIED
sudoRunAsUser: %group_user2: ALLOWED
sudoRunAsUser: %group_user1: DENIED
sudoRunAsUser: +netgroup_user2: ALLOWED
sudoRunAsUser: +netgroup_user1: DENIED
sudoRunAsGroup: group_user2: ALLOWED
sudoRunAsGroup: group_user1: DENIED
sudoRunAsGroup: #20002: ALLOWED
sudoRunAsGroup: #20001: DENIED
(note the difference in the third line)
Additional info:
The attached patch fixes the problem
Comment 1Nikolai Kondrashov
2012-11-13 15:01:25 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.
http://rhn.redhat.com/errata/RHBA-2013-0363.html
Created attachment 644161 [details] Patch fixing the problem Description of problem: sudoRunAsUser #uid values match users neither with LDAP nor with SSSD backends Version-Release number of selected component (if applicable): sudo-1.8.6p3-5.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Use the attached LDIF file to fill a LDAP directory. 2. Use the attached sssd.conf as the base for SSSD configuration. 3. Execute the attached sudo_runas_spec_test with "ldap" or "sssd" argument depending on the configured backend. Actual results: sudoRunAsUser: user2: ALLOWED sudoRunAsUser: user1: DENIED sudoRunAsUser: #10002: DENIED sudoRunAsUser: #10001: DENIED sudoRunAsUser: %group_user2: ALLOWED sudoRunAsUser: %group_user1: DENIED sudoRunAsUser: +netgroup_user2: ALLOWED sudoRunAsUser: +netgroup_user1: DENIED sudoRunAsGroup: group_user2: ALLOWED sudoRunAsGroup: group_user1: DENIED sudoRunAsGroup: #20002: ALLOWED sudoRunAsGroup: #20001: DENIED (note the third line) Expected results: sudoRunAsUser: user2: ALLOWED sudoRunAsUser: user1: DENIED sudoRunAsUser: #10002: ALLOWED sudoRunAsUser: #10001: DENIED sudoRunAsUser: %group_user2: ALLOWED sudoRunAsUser: %group_user1: DENIED sudoRunAsUser: +netgroup_user2: ALLOWED sudoRunAsUser: +netgroup_user1: DENIED sudoRunAsGroup: group_user2: ALLOWED sudoRunAsGroup: group_user1: DENIED sudoRunAsGroup: #20002: ALLOWED sudoRunAsGroup: #20001: DENIED (note the difference in the third line) Additional info: The attached patch fixes the problem