Your message dated Wed, 14 Nov 2007 08:29:13 -0800 (PST)
with message-id <[EMAIL PROTECTED]>
and subject line libpam-ldap: add comments to the config file
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libpam-ldap
Version: all
severity: wishlist
In /etc/pam_ldap.conf there is:
# The distinguished name to bind to the server with
# if the effective user ID is root. Password is
# stored in /etc/ldap.secret (mode 600)
Well, that's only half the truth. The password stored there must not
have a newline at the end nor a blank. But what strikes most is
that it must not be a terminated line, so creating the password with
e.g. vi will not work!
I would vote for adding a hint to the above comment:
# The distinguished name to bind to the server with
# if the effective user ID is root. Password is
# stored in /etc/ldap.secret (mode 600). Use
# 'echo -n mYpAsSwOrD > /etc/ldap.secret' instead of an
# editor to create it.
rgds,
Andreas John
--
Andreas John
net-lab GmbH
Luisenstrasse 30b
63067 Offenbach
Tel: +49 69 85700331
http://www.net-lab.net
--- End Message ---
--- Begin Message ---
I'm not sure what version you were using at the time (the report says
'all'), but /etc/(pam|libnss)_ldap.secret does need the password line
terminated normally (and thus *is* editable via vi)
--
Rick Nelson
"...you might as well skip the Xmas celebration completely, and instead
sit in front of your linux computer playing with the
all-new-and-improved linux kernel version."
(By Linus Torvalds)
--- End Message ---
