Package: nslcd Version: 0.7.15+squeeze3 Severity: grave This may be related/the same as #696445. I didn't want to hijack the thread with an unrelated bug just in case. I do believe this (and the other bug should be tagged as grave). This essentially locks you out of ssh (if you rely on a user within ldap) upon next nslcd restart/reboot. Depending on your setup (remote/cloud etc), this can effectively render your machine useless.
This may have existed for a while and not be related to the recent update. I thought someone was screwing with nslcd.conf and not telling me when they realised it broke but it was probably updating that did it. Originally: nslcd: 0.7.15+squeeze2 file: nslcd.orig After installing nslcd: 0.7.15+squeeze3 file nslcd.conf diff nslcd.* 16c16 < base ou=groups,dc=example,dc=com --- > base ou=users,ou=users,dc=example,dc=com I'm attaching md5sums so you can validate you have exact copies. 33a27616d645dba2309cc2747f29e400 nslcd.conf cfc79d3f9958a994ff6a302b5e894976 nslcd.orig
nslcd.conf
Description: Binary data
nslcd.orig
Description: Binary data
