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.
Created attachment 859192[details]
Buffer size patch
Description of problem:
The buffer sizes in the version 0.7.5 are too small, especially if you have a long GECOS field in the LDAP. The upstream has changed the buffer sizes already with https://github.com/arthurdejong/nss-pam-ldapd/commit/373a1535130bc18ddcb3da38c9b429149756669b
Version-Release number of selected component (if applicable):
nss-pam-ldapd-0.7.5-18.2.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create user account with "long" GECOS string (> 100 bytes)
2. getent passwd username
Actual results:
Empty GECOS field
Expected results:
Actual GECOS field from LDAP
Users from different auth providers should be different. They are from different domains. It is security issue to use short user names in multi domain setup because one user can mask another. So it is not a problem with SSSD it is a problem with setup.
SSSD would not fix nss-pam-ldapd but the priority of fixing nss-pam-ldapd is extremely low because it is going to be replaced by SSSD eventually.
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://rhn.redhat.com/errata/RHBA-2016-0758.html
For the benefit of others who might be searching for this: messages such as the following in /var/log/messages indicate that you may be hitting this bug.
Jul 6 07:38:01 hostname nslcd[2868]: [4461f7] attribute mapping "${gecos:-$cn}" is invalid
Jul 6 07:38:24 hostname nslcd[2868]: [1335c9] attribute mapping "${gecos:-$cn}" is invalid
Jul 6 07:42:05 hostname nslcd[2868]: [6545a9] attribute mapping "${gecos:-$cn}" is invalid