Bug 164413 - libuser:lchsh with ldap module dies with simple bind
Summary: libuser:lchsh with ldap module dies with simple bind
Status: CLOSED DUPLICATE of bug 164958
Alias: None
Product: Fedora
Classification: Fedora
Component: libuser
Version: 4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-27 19:30 UTC by Gary Molenkamp
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2005-08-03 02:35:04 UTC


Attachments (Terms of Use)

Description Gary Molenkamp 2005-07-27 19:30:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922

Description of problem:
When I use lchsh or lchfn as root on an existing user in my ldap db, I am prompted for the binddn and then the app exits.

[root@db ~]# lchsh gary
Changing shell for gary.
LDAP Bind Password:
[root@db ~]#

/etc/libuser.conf sections look like:

[defaults]
modules = files ldap
create_modules = ldap
...
[ldap]
# Setting these is always necessary.
#server = 127.0.0.1
server = ldap://localhost:389
basedn = dc=example,dc=com
bindtype = simple
binddn = cn=Manager,dc=example,dc=com

Using other tools to verify the entry is successful:
   ldapsearch -b 'dc=example,dc=com' -x -W -D 'cn=Manager,dc=example,dc=com' -H ldap://127.0.0.1:389 uid=gary loginShell




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

How reproducible:
Always

Steps to Reproduce:
1. lchsh gary
2.
3.
  

Actual Results:  App exited

Expected Results:  prompt for new shell

Additional info:

Comment 1 Gary Molenkamp 2005-07-29 17:52:35 UTC
Seems that libuser was still trying to use TLS but not producing any error output.
Commenting out the ldap_start_tls_s call allows the expected behaviour.

Comment 2 Miloslav Trmač 2005-08-03 02:35:04 UTC
Thanks for your report.

The program dies with SIGPIPE; bash normally does not report this because
it happens often with pipelines.

This is caused by a bug in the ldap server; a workaround is to configure
your ldap server to support TLS.

*** This bug has been marked as a duplicate of 164958 ***


Note You need to log in before you can comment on or make changes to this bug.