Bug#472872: myldap_has_objectclass(): myldap_get_values() returned NULL in syslog

2008-04-04 Thread Arthur de Jong
On Sun, 2008-03-30 at 07:17 +1100, Alex Samad wrote: That would be a solution but not something I would want to implement. If it were some sort of search already I could add it but since this is an attribute lookup like any other. shouldn't be that hard to do, from my limit knowledge of

Bug#472872: myldap_has_objectclass(): myldap_get_values() returned NULL in syslog

2008-04-04 Thread Alex Samad
On Fri, Apr 04, 2008 at 11:34:38PM +0200, Arthur de Jong wrote: On Sun, 2008-03-30 at 07:17 +1100, Alex Samad wrote: That would be a solution but not something I would want to implement. If it were some sort of search already I could add it but since this is an attribute lookup like

Bug#472872: myldap_has_objectclass(): myldap_get_values() returned NULL in syslog

2008-03-29 Thread Alex Samad
On Sat, Mar 29, 2008 at 12:04:39AM +0100, Arthur de Jong wrote: tags 472872 + pending thanks First of all to reply to your earlier mail, reporting bugs is fine for me and makes it easy to track. On Thu, 2008-03-27 at 10:24 +1100, Alex Samad wrote: Seems like libnss-ldapd checks for

Bug#472872: myldap_has_objectclass(): myldap_get_values() returned NULL in syslog

2008-03-28 Thread Arthur de Jong
tags 472872 + pending thanks First of all to reply to your earlier mail, reporting bugs is fine for me and makes it easy to track. On Thu, 2008-03-27 at 10:24 +1100, Alex Samad wrote: Seems like libnss-ldapd checks for object class by reading a ldapobject in and then checking the objectclass

Bug#472872: myldap_has_objectclass(): myldap_get_values() returned NULL in syslog

2008-03-26 Thread Alex Samad
Package: libnss-ldapd Version: 0.6 Severity: important Seems like libnss-ldapd checks for object class by reading a ldapobject in and then checking the objectclass attribute for a specific record. On my ldap setup I do not allow for objectclass to be read by any user, you can search. This causes