Re: ldapi PATH oddity

[Pierangelo Masarati <ando@sys-net.it>]

Dieter Kluenter wrote:

> Rich Graves <rcgraves@brandeis.edu> writes:
>
>  
>
> > openldap 2.2.14 on Linux RedHat Enterprise 3.
> >
> > I'm doing anonymous simple binds over ldapi:///. On my test machine, 
> > everything including an ACL based on peername.path="/var/run/ldapi" work.
> >
> > When I moved it to a production machine, the ACL failed, and logs show 
> > gibberish IPC PATH like the below.
> >
> > As far as I can tell, the only difference between the machines is that the
> > production machine has multiple CPUs. The running binaries, slapd.conf, and
> > kernel versions seem to be the same.
> >
> > Jul 29 14:26:38 blanca slapd[22123]: conn=141 fd=19 ACCEPT from PATH=§o\201@c£ (PATH=/var/run/ldapi)
> >    
> [...]
>
> You should escape your path, that is
> ldapi://%2Fvar%2Frun%2Fldapi
>  
I think the problem is elsewhere; if it got to the logs, with the right 
listener logged
between round brackets, the problem is actually in the string being 
logged right
before, which comes from the sun_path member of the local sockaddr 
struct.  See
my recent fix to servers/slapd/daemon.c in HEAD.

p.



   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497