misc/108033: ls coredumps when nss/ldap is misconfigured

[Gerrit Kühn]

>Number:         108033
>Category:       misc
>Synopsis:       ls coredumps when nss/ldap is misconfigured
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 17 12:10:17 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Gerrit Kühn
>Release:        7.0
>Organization:
Universität Hannover
>Environment:
FreeBSD eclipse.aei.uni-hannover.de 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Thu Dec 21 15:28:56 CET 2006     root at eclipse.aei.uni-hannover.de:/usr/obj/usr/src/sys/ECLIPSE  i386

>Description:
After reading (and mixing up :-) various hints I found on the web for setting up ldap, pam_ldap and nss_ldap, I ended up with a softlink from ldap.conf pointing to nss_ldap.conf and mode 600 for this file.
This causes ls to coredump as soon as any uid/gid are processed:

[I have no name!@eclipse ~]$ ls -l
Assertion failed: (cfg->ldc_uris[__session.ls_current_uri] != NULL), function do_init, file ldap-nss.c, line 1312.
Abort trap: 6 (core dumped)

>How-To-Repeat:
Make nss_ldap.conf unreadable for the user and try to list anything with ldap uid/gid (using ls -la or similar).
>Fix:
The obvious solution is to make nss_ldap readable. However, imho ls should not coredump in this situation. This may also be a problem of net/nss_ldap.

>Release-Note:
>Audit-Trail:
>Unformatted: