[Bug 1350778] Re: Upgrading nslcd on precise rewrites /etc/nslcd.conf, leaving users with unusable systems
Robie Basak
1350778 at bugs.launchpad.net
Thu Sep 25 14:03:49 UTC 2014
*** This bug is a duplicate of bug 1229713 ***
https://bugs.launchpad.net/bugs/1229713
It seems to me that bug 1229713 is a duplicate, or at least that the fix
there will fix the original issue described in this bug. So I've
uploaded the fix from there, as that bug already had a debdiff that
looked good with all the correct SRU information filled out in that bug.
I'll mark this bug as a duplicate.
If I'm wrong, please correct me.
** This bug has been marked a duplicate of bug 1229713
nslcd auto-configuration disregards existing nslcd.conf
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1350778
Title:
Upgrading nslcd on precise rewrites /etc/nslcd.conf, leaving users
with unusable systems
Status in “nss-pam-ldapd” package in Ubuntu:
Confirmed
Bug description:
Ubuntu release: 12.04.1
Package version: 0.8.4ubuntu0.2 and 0.8.4ubuntu0.3
We use ldap for user auth. Our /etc/nslcd.conf needed to be customised
with certain tls and ssl options. Here's what the relevant parts
looked like:
# The location at which the LDAP server(s) should be reachable.
uri ldaps://ldap.internal/
# SSL options
ssl yes
# needed for internal ldap to connect
tls_reqcert allow
The security update in 0.8.4ubuntu0.3 was installed.
What I expected to happen: The configuration should have been left as
it was.
What actually happened: the options ended up like this:
# The location at which the LDAP server(s) should be reachable.
uri ldaps://127.0.0.1/
# SSL options
ssl yes
# needed for internal ldap to connect
#tls_reqcert allow
This left us unable to log in to any of our servers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1350778/+subscriptions
More information about the Ubuntu-sponsors
mailing list