[Date Prev][Date Next]
(ITS#3663) No timeout in ldap binds
Full_Name: David Le Corfec
Submission from: (NULL) (18.104.22.168)
Any news regarding the lack of a timeout in ldap bind ?
A NULL timeval is supplied to ldap_result()
if ( ldap_result( ld, msgid, 1, NULL, &result ) == -1 )
In effect, a select() will wait forever.
I understand that it would require an API change, as discussed
Even if it had a sensible default timeout or a global setting ?
The problem is that it's currently possible to hang local
and remote logins using unix or ldap accounts to all machine
depending on a LDAP server which doesn't answer past
the TCP connection ... (can be simulated by sending SIGSTOP to slapd :)
Already happened several times this week for various reasons :(