Displaying 3 results from an estimated 3 matches for "cldap_search_send".
Did you mean:
ldap_search_send
2016 Oct 17
2
Bug 6870 resurfaced in Samba 4.2.10
On Mon, Oct 17, 2016 at 09:41:10AM -0700, Jeremy Allison via samba wrote:
> On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote:
> >
> >
> > Hi,
> >
> > So I did some digging into the source code, and I think I've found the
> > issue. Around line 120 of source3/libads/cldap.c:
> >
> > for (i=0; i<num_servers;
2016 Oct 17
0
Bug 6870 resurfaced in Samba 4.2.10
...now if it fixes your test case ?
CC:ing to samba-technical for followups.
Cheers,
Jeremy.
Results not good m'fraid.
It seems cldap_socket_init() should be setting up the cldap_socket
(param 3 is struct cldap_socket **), but obviously doesn't get this far.
When this is passed to cldap_search_send() it segfaults on line 603:
if (!cldap->connected) {
This is going to be icky, isn't it?
Regards
Rebecca Gellman
2016 Oct 17
2
Bug 6870 resurfaced in Samba 4.2.10
...-technical for followups.
>
> Cheers,
>
> Jeremy.
>
> Results not good m'fraid.
>
> It seems cldap_socket_init() should be setting up the cldap_socket
> (param 3 is struct cldap_socket **), but obviously doesn't get this far.
> When this is passed to cldap_search_send() it segfaults on line 603:
>
> if (!cldap->connected) {
>
> This is going to be icky, isn't it?
No, it's not so bad. libcli/cldap/cldap.c is clearly supposed to cope
with caller.cldap == NULL - you can see this in the function
cldap_search_state_destructor() which chec...