hyc(a)symas.com wrote in ITS#8240:
> Our patch response was too hasty. There is no OpenLDAP bug here, the real
> issue is production binaries being built with asserts enabled instead of
> compiling with -DNDEBUG. That's an issue for packagers and distros to resolve.
> Closing this ITS, not an OpenLDAP bug.
Maybe I missed something. But this is the first time I've heard about -DNDEBUG
being mandatory when compiling binary packages for production use. Does it
have other effects?
And what are general rules for assert statements in OpenLDAP code?
In my own (Python) code assert statements are supposed to be only triggered if
something goes wrong *internally* (type issues etc.). If somebody manages to
trigger an assert statement with invalid input from "outside" I always
consider this to be a serious bug revealing insufficient error handling even
though e.g. web2ldap just logs the exception but won't crash. YMMV, but please
I also wonder whether there are more mandatory rules for building packages and
where I can find them.
Please don't get me wrong: My inquiry is in good faith to avoid unnecessary
ITS based on misunderstanding.
There have been some reports coming in to the ITS system that likely should
go into OpenLDAP 2.4.48/LMDB 0.9.23. These are:
ITS#8969 - Tweak to LMDB page splits (already committed to LMDB RE0.9)
ITS#8968 - ASYNC connect mode does not work on Solaris
ITS#8967 - back-mdb "unchecked" limits broken with particular search
scopes. Needs fix.
ITS#8957 - ASYNC TLS mode is broken
ITS#8963 - StartTLS failures with back-ldap due to bug in timeout
calculation. Needs fix.
ITS#8472 - only do index DB cleanup if DB is running (fix committed to
ITS#8952 - High CPU usage when idletime is < 4 (fix committed to master)
Any objections to me syncing these over into RE24?
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
I am actually writing a package for OpenIndiana.
The automatic test routine may use the test target in the Makefile.
What does the test target output mean?
How can I see that the test passed successfully?
As far as I saw up to now the outout seems to be supposed to differ in some lines…
Can someone help me there?
Thanks in advance.
I'd like TLS version/cipher logged with "TLS established", so I've
cherry-picked these commits to our RE24 installation:
7d6d694 ITS#7683 log tls prot/cipher info
0045e56 ITS#7683 more for tls version/cipher info
Also this looks like it should go with them, though we use OpenSSL:
7a7d941 ITS#7979 MozNSS fix for TLS_PROTOCOL_MIN
Do anyone remember if this is complete, or if any fixups are needed?
I've not spotted any more commits, anyway.
As discussed yesterday we could run a stand at FOSDEM which takes place
2 & 3 February 2019 at Brussels.
The CfP for various kinds of contributions:
Application form for a stand:
I'd be willing to spend some time at an OpenLDAP booth.
@Howard: Would you like to apply for it?
I'm not sure whether somebody requested a IAM devroom again.
Will try to monitor that.