I'll test your patch on a 2.5STABLE7. I'll let you know about the results.
Bugzilla # is 1187 By the way I use these filters : auth_param basic program /proxy1/libexec/squid_ldap_auth -b ou=Person,dc=company,dc=com -f(uid=%s) -h ldapserver external_acl_type ldap_group %LOGIN /proxy1/libexec/squid_ldap_group -b ou=Applications,dc=company,dc=com -B ou=Person,dc=company,dc=com -F "(uid=%s)" -f "(&(uniqueMember=%u)(cn=%g)(objectClass=groupofuniquenames))" -h ldapserver Thanks Andrew. >> The best would be that Squid asks for a username/passwd until it is valid (good pair && no whitespace) so that the end-user doesn't get confused. > >Then make sure the authentication helper rejects logins with spaces in >them. > > > On Fri, 7 Jan 2005, Henrik Nordstrom wrote: > > > On Fri, 7 Jan 2005 [EMAIL PROTECTED] wrote: > > > >> I am using squid_ldap_auth as shipped with squid 2.5stable5 > >> and also squid_ldap_group but that's out of topic. > > > > Hmm.. What LDAP server are you using, with what user filter to > > squid_ldap_auth? > > > > Also try with a more current version. There was significant changes in > > related areas for the 2.5.STABLE6 release (bug #935). This doesn'e > explicitly > > deal with space characters however.. > > > > A quick test with LDAP search tools reveals this is a bit problematic as > the > > LDAP server ignores the amount of spaces in logins.. Please try the > attached > > patch. > > And please also file a bugreport so I have a bug to attach the patch to > to make sure it doesn't get forgotten before 2.5.STABLE8 is released. > > Regards > Henrik >
