Bug#375533: Assertion failure in libnss-ldap

2006-09-29 Thread Steinar H. Gunderson
On Tue, Sep 26, 2006 at 01:29:40PM +0300, Damyan Ivanov wrote: Just wanted to confirm that changing /etc/libnss-ldap.conf's permissions to 0644 fixes the problem. But how did it get to 0600 in the first place? The postinst installs it to 0644... Did you ever change this? I'm unable to reproduce

Bug#375533: Assertion failure in libnss-ldap

2006-09-29 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steinar H. Gunderson написа: On Tue, Sep 26, 2006 at 01:29:40PM +0300, Damyan Ivanov wrote: Just wanted to confirm that changing /etc/libnss-ldap.conf's permissions to 0644 fixes the problem. But how did it get to 0600 in the first place? The

Bug#375533: Assertion failure in libnss-ldap

2006-09-29 Thread Steinar H. Gunderson
On Fri, Sep 29, 2006 at 04:36:30PM +0400, Damyan Ivanov wrote: It asks here via debconf. Perhaps the question is asked only the first time the package in installed. dpkg-reconfigure makes it ask the question again. Hm. The template says: _Description: make configuration readable/writeable

Bug#375533: Assertion failure in libnss-ldap

2006-09-29 Thread Steinar H. Gunderson
severity 375533 normal tanks On Fri, Sep 29, 2006 at 03:10:18PM +0200, Steinar H. Gunderson wrote: So if you explicitly set it, and then stop nscd, it will break. That's not really anything libnss-ldap can do anything about, is it? I'm downgrading this; I can't find that it would be RC, given

Bug#375533: Assertion failure in libnss-ldap

2006-09-26 Thread Damyan Ivanov
Hi, Just wanted to confirm that changing /etc/libnss-ldap.conf's permissions to 0644 fixes the problem. To do this properly, I had to re-configure the package (dpkg-reconfigure libnss-ldap), since hand-fixed perms get reset on upgrade. Does libnss-ldap.conf need to be 0600 at all? As far as I