[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4387) slapd-ldap backend leaks descriptors on closed connections on x86_64



On 2/5/06, Pierangelo Masarati <ando@sys-net.it> wrote:
> I mean: if all it performs is binds then I'd agree; but if it performs
> anything else in between, then it's a poor design, because the identity
> that's used for the other operations would change after each
> (successful) bind.

>From the logs I can see, that it binds as the special mail server user
when it needs to look up account information, and binds as other users
when it needs to test their password.

So it typically looks like this:

connection1:
bind as user bob
bind as user alice
bind as user CourierMTA
search for mail=gregory@example.com attributes homeDirectory, cn,
uidNumber, gidNumber etc.
bind as user bob
...

connection2:
bind as user CourierMTA
search for mail=bob@example.com attributes homeDirectory, cn,
uidNumber, gidNumber etc.
bind as user alice
bind as user alice
...

Seems like it behaves correctly.

--
    Aleksander Adamowski
        Jabber JID: olo@jabber.altkom.pl
        GG#: 274614
        ICQ UIN: 19780575
        http://olo.ab.altkom.pl