Bug#620235: Dont resolve user in ldap

2011-04-03 Thread Arthur de Jong
On Sun, 2011-04-03 at 23:39 +0400, Alexander GQ Gerasiov wrote: > May be refer to documentation or config option wich specify this. > Well simple "username is not allowed by regexp > user_regexp_config_variable" is much more informative. I just need > keyword to look for in manual. Thanks for the

Bug#620235: Dont resolve user in ldap

2011-04-03 Thread Alexander GQ Gerasiov
Hello, Arthur. On Sun, 03 Apr 2011 21:03:08 +0200 Arthur de Jong wrote: > On Fri, 2011-04-01 at 11:12 +0400, Alexander GQ Gerasiov wrote: > > > The cause of this problem is the new regular expression based > > > checks for valid usernames. It currently rejects usernames of > > > less than three

Bug#620235: Dont resolve user in ldap

2011-04-03 Thread Arthur de Jong
On Fri, 2011-04-01 at 11:12 +0400, Alexander GQ Gerasiov wrote: > > The cause of this problem is the new regular expression based checks > > for valid usernames. It currently rejects usernames of less than three > > characters. This will be fixed in the next release (the minimum will > > be two the

Bug#620235: Dont resolve user in ldap

2011-04-01 Thread Alexander GQ Gerasiov
Thu, 31 Mar 2011 21:24:32 +0200 Arthur de Jong wrote: > retitle 620235 problems with short usernames > tags 620235 + pending > thanks > > On Thu, 2011-03-31 at 14:50 +0400, Alexander Gerasiov wrote: > > Today nslcd upgraded to 0.8.2 and I catched the following bug. > > > > It fails to resolve u

Bug#620235: Dont resolve user in ldap

2011-03-31 Thread Arthur de Jong
retitle 620235 problems with short usernames tags 620235 + pending thanks On Thu, 2011-03-31 at 14:50 +0400, Alexander Gerasiov wrote: > Today nslcd upgraded to 0.8.2 and I catched the following bug. > > It fails to resolve username 'gq' in ldap. Other users works fine. > Looks like it doesn't lo

Bug#620235: Dont resolve user in ldap

2011-03-31 Thread Alexander Gerasiov
Package: nslcd Version: 0.8.2 Severity: important Tags: experimental Hi there. Today nslcd upgraded to 0.8.2 and I catched the following bug. It fails to resolve username 'gq' in ldap. Other users works fine. Looks like it doesn't look in ldap at all: nslcd: [8b4567] DEBUG: connection from pid=