This is a limitation of Squid's configuration file parser.
To work around it you can wrap squid_ldap_auth in a small shell script
providing the correct arguments.
authenticate_program /path/to/your/shell/wraper.sh
--- wrapper.sh ---
#!/bin/sh
exec /path/to/squid_ldap_auth arguemnts....
It is on the todo to fix Squid's configuration parser to handle spaces
and other "odd" characters in a clean manner, but it is not there yet.
-- Henrik Nordstrom Squid Hacker Frank Schmirler wrote: > > I did a little bit of testing with the new squid_ldap_auth module. > Everything worked fine so far. Definitly a big advance compared to the > old version! > > Just one thing I stumbled over: What do you do if the binddn contains > space characters (like cn=Squid Cache,cn=...). I tried to quote it > and tried a backslash-escape it. Both works fine on the command line > but squid obviously doesn't know about these escapes when parsing the > authenticator_program params. Are there any other escapes? > > I also tried to replace the space character by %20 but this also didn't > work. This might be a way to bypass the problem with the > authenticator_program params. > > FrankReceived on Wed May 30 2001 - 01:31:10 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:00:20 MST