+++ This bug was initially created as a clone of Bug #448883 +++ Description of problem: dhcp-lab-198 newman # getent -s 'ldap' passwd Segmentation fault Version-Release number of selected component (if applicable): glibc-common-2.3.4-2.39 How reproducible: always Actual results: segfault Expected results: error msg, clear result, ... it depends Additional info: OpenLDAP is installed. It segfaults or and without OpenLDAP being running.
nss_ldap-253-3.el4 from 4.7
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: If the hostname resolution was configured to use 'ldap' only, it was impossible to resolve a hostname of the target LDAP server to its address without contacting it. This caused a recursion in the underlying nss_ldap module until a segmentation fault occurred and the calling application crashed. The updated nss_ldap package ensures that no segmentation fault occurs.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -If the hostname resolution was configured to use 'ldap' only, it was impossible to resolve a hostname of the target LDAP server to its address without contacting it. This caused a recursion in the underlying nss_ldap module until a segmentation fault occurred and the calling application crashed. The updated nss_ldap package ensures that no segmentation fault occurs.+If the hostname resolution was configured to use 'ldap' only, it was impossible to resolve a hostname of the target Lightweight Directory Access Protocol (LDAP) server to its address without contacting it. This caused a recursion in the underlying nss_ldap module until a segmentation fault occurred and the calling application crashed. The updated nss_ldap package ensures that no segmentation fault occurs.
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-0239.html