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 1425790 - Unable to authenticate with 64 character password using nss-pam-ldapd
Summary: Unable to authenticate with 64 character password using nss-pam-ldapd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nss-pam-ldapd
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Martin Zelený
URL:
Whiteboard:
: 1536135 (view as bug list)
Depends On:
Blocks: 1420851 1773506
TreeView+ depends on / blocked
 
Reported: 2017-02-22 12:48 UTC by Andrey Bondarenko
Modified: 2021-03-11 14:59 UTC (History)
4 users (show)

Fixed In Version: nss-pam-ldapd-0.8.13-12.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1773506 (view as bug list)
Environment:
Last Closed: 2018-04-10 17:24:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0935 0 None None None 2018-04-10 17:25:33 UTC

Description Andrey Bondarenko 2017-02-22 12:48:21 UTC 
Description of problem:


A user with a 64 character password fails when trying to authenticate.

/var/log/messages:
    Feb 21 10:07:40 new1 sudo: pam_ldap(sudo-i:auth): error reading from nslcd: Connection reset by peer
    Feb 21 10:07:43 new1 sudo: pam_ldap(sudo-i:auth): error reading from nslcd: Connection reset by peer
    Feb 21 10:07:46 new1 sudo: pam_ldap(sudo-i:auth): error reading from nslcd: Connection reset by peer

Running nslcd in debug mode:
[root@new1 ~]# nslcd -d
nslcd: DEBUG: add_uri(ldaps://authentication2.host.net/)
nslcd: DEBUG: add_uri(ldaps://authentication1.host.net/)
nslcd: DEBUG: ldap_set_option(LDAP_OPT_X_TLS_CACERTDIR,"/etc/openldap/cacerts")
nslcd: version 0.8.13 starting
nslcd: DEBUG: unlink() of /var/run/nslcd/socket failed (ignored): No such file or directory
nslcd: DEBUG: initgroups("nslcd",55) done
nslcd: DEBUG: setgid(55) done
nslcd: DEBUG: setuid(65) done
nslcd: accepting connections
nslcd: DEBUG: accept() failed (ignored): Resource temporarily unavailable
nslcd: [8b4567] DEBUG: connection from pid=18320 uid=0 gid=600
nslcd: [8b4567] client supplied argument 1 bytes too large


Version-Release number of selected component (if applicable):

 nss-pam-ldapd-0.8.13-8.el7.x86_64

How reproducible:

 Have user with 64 characters in password.

Steps to Reproduce:
1. Configure system to use nslcd for the auth
2. Set up user with password longer then 64 chars
3. Try auth

Actual results:

fail

Expected results:

authentication

Additional info:

In 5 and 6 not reproducible.
Comment 8 Jakub Hrozek 2018-03-20 10:10:47 UTC 
*** Bug 1536135 has been marked as a duplicate of this bug. ***
Comment 10 errata-xmlrpc 2018-04-10 17:24:59 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:0935
Note You need to log in before you can comment on or make changes to this bug.