openldap-bugs July 2026

openldap-bugs@openldap.org

1 participants
45 discussions

[Issue 10547] New: PLeas change company name and url under Support
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10547 Issue ID: 10547 Summary: PLeas change company name and url under Support Product: website Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: website Assignee: bugs(a)openldap.org Reporter: info(a)allskills-training.com Target Milestone: --- Hallo, we are listed as Support/Training Center under: https://www.openldap.org/support/ We are named formerly (old name): SMLAN Software & Management Training New Company Name (changed): allskills Training Link to our Website - OpenLDAP Training: https://www.allskills-training.com/seminarthemen/alle/ldap-directory-servic… Pleas can you change our Company name and Website-URL. Thanks for your help and greetings from germany Guenter -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10546] New: ldap_explode_dn result is not released in the interactive test client
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10546 Issue ID: 10546 Summary: ldap_explode_dn result is not released in the interactive test client Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: libraries Assignee: bugs(a)openldap.org Reporter: 1489378385(a)qq.com Target Milestone: --- URL: https://github.com/openldap/openldap/blob/8afcbe9e04f1a40f03cea51c57418b05f… Description: Source revision: 8afcbe9e04f1a40f03cea51c57418b05f86e8f44 Affected file: libraries/libldap/test.c Affected lines: 472-478 Source-level observation: The interactive test client's E command calls ldap_explode_dn() and stores the returned NULL-terminated array in exdn. It prints the array elements and then leaves the switch case without releasing exdn. According to ldap_get_dn(3), the result returned by ldap_explode_dn() should be released with ldap_value_free(). The only reference to the allocated array is overwritten the next time the E command is executed. Steps to verify: 1. Build the libraries/libldap interactive test client with AddressSanitizer or LeakSanitizer enabled. 2. Start the test client. 3. Execute the E command and enter a valid DN, for example: cn=test,dc=example,dc=com 4. Repeat the E command several times. 5. Exit the client and inspect the sanitizer report or monitor its memory use. Actual result: Each E command allocates an exploded DN array that remains allocated until the process terminates. Expected result: The exploded DN array should be released after all of its elements have been printed. Impact: Repeated use of the E command increases the test client's memory consumption. Validation status: Confirmed by source review at the revision above. Runtime sanitizer validation is pending. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10545] New: urltest leaks the parsed LDAPURLDesc and reconstructed URL string
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10545 Issue ID: 10545 Summary: urltest leaks the parsed LDAPURLDesc and reconstructed URL string Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: libraries Assignee: bugs(a)openldap.org Reporter: 1489378385(a)qq.com Target Milestone: --- URL: https://github.com/openldap/openldap/blob/8afcbe9e04f1a40f03cea51c57418b05f… Description: Source revision: 8afcbe9e04f1a40f03cea51c57418b05f86e8f44 Affected file: libraries/libldap/urltest.c Affected lines: 75 and 125-127 Source-level observation: On a successful call, ldap_url_parse() allocates an LDAPURLDesc and stores it in lud. The program reaches its final return without calling ldap_free_urldesc(lud). There is also a second allocation on line 125: fprintf(stdout, "URL: %s\n", ldap_url_desc2str(lud)); ldap_url_desc2str() allocates its returned string with LDAP_MALLOC. Because the return value is passed directly to fprintf(), its pointer is lost and the string cannot be released. Steps to verify: 1. Build libraries/libldap/urltest with AddressSanitizer or LeakSanitizer. 2. Run it with a valid URL, for example: ./urltest 'ldap://localhost/dc=example,dc=com??sub?(objectClass=*)' 3. Allow the program to exit successfully. 4. Inspect the sanitizer report. Actual result: A successful invocation exits without releasing either the LDAPURLDesc or the string returned by ldap_url_desc2str(). Expected result: Both allocations should be released before returning from main(). Impact: Each successful run leaves two process-lifetime allocations. The practical impact is low because urltest is a short-lived test utility, but the ownership contracts are not followed and leak detectors report the allocations. Validation status: Confirmed by source review at the revision above. Runtime sanitizer validation is pending. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10542] New: On Windows, allow using previous write behavior
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10542 Issue ID: 10542 Summary: On Windows, allow using previous write behavior Product: LMDB Version: 1.0.0 Hardware: All OS: Windows Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- ITS#9017 changed write behavior in Windows to use WRITE_THROUGH writes and eliminate use of FlushFileBuffers(). Supposedly this yields faster write performance because flushes are very slow. However, other users report this approach is actually much slower than LMDB 0.9. Add a compile-time flag to revert to the original write behavior. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10544] New: slapd-bind parses the -B search URL but neither uses nor frees it
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10544 Issue ID: 10544 Summary: slapd-bind parses the -B search URL but neither uses nor frees it Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: test suite Assignee: bugs(a)openldap.org Reporter: 1489378385(a)qq.com Target Milestone: --- URL: https://github.com/openldap/openldap/blob/8afcbe9e04f1a40f03cea51c57418b05f… Description: Source revision: 8afcbe9e04f1a40f03cea51c57418b05f86e8f44 Affected file: tests/progs/slapd-bind.c Affected lines: 98, 116-143, and 182-190 Source-level observation: When -B search=<LDAP URL> is supplied, ldap_url_parse() allocates an LDAPURLDesc and stores it in extra_ludp. After parsing, extra_ludp is not referenced again. In particular, the calls to do_base() and do_bind() pass an action type of -1 and an action pointer of NULL instead of passing TESTER_SEARCH and extra_ludp. The descriptor is also not released before exit(EXIT_SUCCESS). Steps to verify: 1. Build slapd-bind with AddressSanitizer or LeakSanitizer. 2. Run slapd-bind with the required connection arguments and a valid option such as: -B 'search=ldap:///dc=example,dc=com??sub?(objectClass=*)' 3. Allow the tester to complete normally. 4. Check whether the requested search action is performed. 5. Inspect the sanitizer report for the LDAPURLDesc allocated by ldap_url_parse(). Actual result: The URL is successfully parsed, but the resulting descriptor is neither used by the bind operation nor released before the process exits. Expected result: The parsed search action should be passed to the relevant test operation and the LDAPURLDesc should be released after the outer test loop completes. Impact: The -B search option appears to have no effect and leaves one LDAPURLDesc allocated until process termination. Validation status: Confirmed by source review at the revision above. Runtime behavior and sanitizer validation are pending. -- You are receiving this mail because: You are on the CC list for the issue.

1 2

[Issue 10538] New: On Windows, a large value write can get silently lost
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10538 Issue ID: 10538 Summary: On Windows, a large value write can get silently lost Product: LMDB Version: 0.9.35 Hardware: x86_64 OS: Windows Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: github(a)nicwatson.org Target Milestone: --- On Windows, mdb_page_flush() writes each overflow page with a single WriteFile() whose write bytes is a 32-bit DWORD. A value whose overflow extent (psize * mp_pages) reaches 2**32 has its length truncated. An extent of exactly 2**32 truncates to 0, so WriteFile() writes nothing and the value is silently lost. The commit still "succeeds" (a 0-byte WriteFile returns TRUE), so the bug shows up as a value that reads back as zeroes instead of its contents. Here's a reproducer. This only works on Windows 64-bit. --- #include <stdio.h> #include <stdlib.h> #include <string.h> #include <direct.h> #define MKDIR(d) _mkdir(d) #include "lmdb.h" #define CHK(expr) do { int rc_ = (expr); if (rc_) { \ fprintf(stderr, "%s:%d: %s: %s\n", __FILE__, __LINE__, #expr, \ mdb_strerror(rc_)); return 2; } } while (0) int main(int argc, char **argv) { const char *dir = argc > 1 ? argv[1] : "lw-repro-db"; const size_t VALSIZE = (size_t)0xFFFFF000UL; MDB_env *env; MDB_txn *txn; MDB_dbi dbi; MDB_val key, val, got; unsigned char *p; char *buf; MKDIR(dir); buf = (char *)malloc(VALSIZE); if (!buf) { fprintf(stderr, "malloc(%zu) failed\n", VALSIZE); return 2; } memset(buf, 'x', VALSIZE); memcpy(buf, "HEAD", 4); memcpy(buf + VALSIZE - 4, "TAIL", 4); CHK(mdb_env_create(&env)); CHK(mdb_env_set_mapsize(env, VALSIZE + (256UL << 20))); CHK(mdb_env_open(env, dir, 0, 0664)); CHK(mdb_txn_begin(env, NULL, 0, &txn)); CHK(mdb_dbi_open(txn, NULL, 0, &dbi)); key.mv_data = (void *)"big"; key.mv_size = 3; val.mv_data = buf; val.mv_size = VALSIZE; CHK(mdb_put(txn, dbi, &key, &val, 0)); CHK(mdb_txn_commit(txn)); /* the overflow-page WriteFile happens here */ free(buf); CHK(mdb_txn_begin(env, NULL, MDB_RDONLY, &txn)); CHK(mdb_get(txn, dbi, &key, &got)); p = (unsigned char *)got.mv_data; if (got.mv_size != VALSIZE || memcmp(p, "HEAD", 4) != 0 || memcmp(p + VALSIZE - 4, "TAIL", 4) != 0) { fprintf(stderr, "BUG REPRODUCED: value truncated/lost: size=%zu " "head=%02x%02x%02x%02x tail=%02x%02x%02x%02x\n", got.mv_size, p[0], p[1], p[2], p[3], p[VALSIZE - 4], p[VALSIZE - 3], p[VALSIZE - 2], p[VALSIZE - 1]); mdb_txn_abort(txn); mdb_env_close(env); return 1; } mdb_txn_abort(txn); mdb_env_close(env); printf("OK: committed and read back %zu-byte value intact\n", VALSIZE); return 0; } -- You are receiving this mail because: You are on the CC list for the issue.

1 8

[Issue 10539] New: LMDB 1.0.0 fails to compile on Windows
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10539 Issue ID: 10539 Summary: LMDB 1.0.0 fails to compile on Windows Product: LMDB Version: 1.0.0 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- Various errors around use of LARGE_INTEGER -- You are receiving this mail because: You are on the CC list for the issue.

1 2

[Issue 10540] New: Clarify "Symas Dual-Use License"
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10540 Issue ID: 10540 Summary: Clarify "Symas Dual-Use License" Product: LMDB Version: 1.0.0 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: keno(a)alumni.harvard.edu Target Milestone: --- Greetings from the Julia project. We recently grew an LMDB dependency (https://github.com/JuliaLang/julia/pull/61527), so I am trying to make sure we have the licensing information correct. In particular, I am wondering about the "Symas Dual-Use License" which is referenced in these files: - crypto.c - cryptoc.c - module.c - mtest_enc{,2,3,4}.c - mtest_remap.c The license header says that a copy of the license is included in the LICENSE file, but this does not appear to be the case. I understand that there was previously an effort to dual license LMDB that did not end up happening (https://github.com/monero-project/meta/issues/85#issuecomment-361925678). Could you clarify if these license headers are a vestigal artifact of that process or if they are currently applicable and if the latter, could the appropriate license text be added to LICENSE? Thanks! Keno -- You are receiving this mail because: You are on the CC list for the issue.

1 6

[Issue 10536] New: Re-fix ITS#8174 mdb_drop(MAIN_DBI)
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10536 Issue ID: 10536 Summary: Re-fix ITS#8174 mdb_drop(MAIN_DBI) Product: LMDB Version: 1.0.0 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- The patch breaks mdb_drop() usability. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10534] New: mdb_env_get_maxkeysize(): requires an _env_open()ed handle
by openldap-its＠openldap.org 21 Jul '26

21 Jul '26

https://bugs.openldap.org/show_bug.cgi?id=10534 Issue ID: 10534 Summary: mdb_env_get_maxkeysize(): requires an _env_open()ed handle Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: steffen(a)sdaoden.eu Target Milestone: --- Created attachment 1174 --> https://bugs.openldap.org/attachment.cgi?id=1174&action=edit git-enabled patch Super minor, but my LMDB implementation for the bogofilter program was buggy because of this. They had to fix it accordingly after almost 8 years, when updating to LMDB 1.0. Suggested fix would be something like - * @param[in] env An environment handle returned by #mdb_env_create() + * @param[in] env An environment handle that is #mdb_env_open() Thanks! And ciao. -- You are receiving this mail because: You are on the CC list for the issue.

1 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs July 2026