[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openldap-bugs
Subject:    [Issue 10147] Bind dn is getting malformed inside ldap_sasl_bind function
From:       openldap-its () openldap ! org
Date:       2024-01-30 10:59:03
Message-ID: bug-10147-2-dI2VQyk48H () http ! bugs ! openldap ! org/
[Download RAW message or body]

https://bugs.openldap.org/show_bug.cgi?id=10147

--- Comment #3 from Ondřej Kuzník <ondra@mistotebe.net> ---
On Tue, Jan 30, 2024 at 10:40:39AM +0000, openldap-its@openldap.org wrote:
> As per the doucmentation, AC_MEMCPY will do the safe copy of memory blocks.
> By default it is calling the memcpy function inside AC_MEMCPY macro(depends on
> the compile time flags HAVE_MEMMOVE,HAVE_BCOPY).
> We replaced AC_MEMCPY with memmove and the issue was resolved and the bind dn
> is parsed as expected.
> 
> memmove will check for overlapping memory locations, whereas memcpy doesn't.
> 
> So, Can we replace this AC_MEMCPY with memmove? Or, Can we enable the
> HAVE_MEMMOVE during compilation?
> If yes, can you please provide some inputs on the impact of this code change.
> Is there any other specific reason behind this abrupt behavior in one server.
> If yes, Kindly let us know so that we will address that one instead of making
> the code change in the above function.

Hi Satish,
seems that ./configure cannot find a usable memmove/bcopy in your build
environment, that's what you want to look into next.

Regards,

-- 
You are receiving this mail because:
You are on the CC list for the issue.=
[prev in list] [next in list] [prev in thread] [next in thread]