Bug#416628: My patch

2007-04-26 Thread Robert Wolf
Hi, maybe it is no bug in real. Because my LDAP user object has no shadowAccount objectClass, libnss-ldap makes "*" in the password field. When I add showAccount objectClass, it make "x" in the password field. When the pam_unix functionality is correct to return SUCCESS on user with "*" in pa

Bug#416628: My patch

2007-04-26 Thread Steve Langasek
reassign 416628 libnss-ldap thanks On Thu, Apr 26, 2007 at 10:42:36AM +0200, Robert Wolf wrote: > > If that isn't what you *want* to have happen, then you seem to have > > misconfigured PAM. > *** The problem is that libnss-ldap version from Sarge returns line: > wolf:x:10001:100:Robert Wolf:/ho

Bug#416628: My patch

2007-04-26 Thread Robert Wolf
Thank you for your answer. On Wed, 25 Apr 2007, Steve Langasek wrote: > On Wed, Apr 25, 2007 at 12:43:27PM +0200, Robert Wolf wrote: > > I am not C & PAM profi programmer, but I think I found a two bugs in PAM > > source > > code regarding to this functionality bug. Both bugs are in the > > Lin

Bug#416628: My patch

2007-04-25 Thread Steve Langasek
On Wed, Apr 25, 2007 at 12:43:27PM +0200, Robert Wolf wrote: > I am not C & PAM profi programmer, but I think I found a two bugs in PAM > source > code regarding to this functionality bug. Both bugs are in the > Linux-PAM/modules/pam_unix/pam_unix_acct.c in the function PAM_EXTERN int > pam_sm_acc

Bug#416628: My patch

2007-04-25 Thread Robert Wolf
Hi anyone, I am not C & PAM profi programmer, but I think I found a two bugs in PAM source code regarding to this functionality bug. Both bugs are in the Linux-PAM/modules/pam_unix/pam_unix_acct.c in the function PAM_EXTERN int pam_sm_acct_mgmt: 1) in the code, there is a condition "if (!strcmp(