Update to last OpenLDAP?

[Neustradamus]

Dear @winlibs team, @cmb69, @weltling, @cmb69, @hyc, @guysoft,

In first, I wish you a Happy New Year 2022!

Can you update to last OpenLDAP version?

Thanks in advance.

[guysoft]

Not my circus, not my monkeys.
contributed some minor code in 2014.

[cmb69]

While an update is due, it might make sense to postpone it until we upgraded to OpenSSL 3, and I'm not even sure whether OpenLDAP 2.6.1 is compatible with OpenSSL 3.

[hyc]

We did some compat work with earlier OpenSSL3 candidates, but at this point we're doing a wait-and-see because OpenSSL3 seems to be getting a lot of negative feedback from the community at large.

[cmb69]

Time flies … I think we need to do an update (2.5.18 or 2.6.8). I haven't looked into OpenSSL 3 support, but now for me the bigger concern is our hand-made build chain. We should really consider to use an environment (Cygwin or MSYS2) which supports autoconf builds.

[cmb69]

I've managed to do a minimalist build (similar to what we have now, but using MSYS2/MSVC) of a patched OpenLDAP 2.5.18 (some of the patches should go upstream; some are very specific for our needs). This needs to be tested, but I don't have an LDAP test setup available. Another hurdle.

Attempting a full client MSYS2/MSVC build of OpenLDAP 2.5.18 failed epicly. :(

[cmb69]

Attempting a full client MSYS2/MSVC build of OpenLDAP 2.5.18 failed epicly. :(

With rxspencer and a couple more patches, it worked. :)

[cmb69]

This needs to be tested, but I don't have an LDAP test setup available.

I've managed to set up slapd so I can run the ext/ldap test suite of PHP. So far, I didn't notice any regressions with the builder having built a patched OpenLDAP 2.5.18. I've also submitted https://bugs.openldap.org/show_bug.cgi?id=10282; let's see where that goes.