openldap-bugs

openldap-bugs@openldap.org

1 participants
21518 discussions

[Issue 10581] New: Mismatch of crypt() prototype on PPC Mac OS X 10.5.8, Leopard
by openldap-its＠openldap.org 08 Sep '26

08 Sep '26

https://bugs.openldap.org/show_bug.cgi?id=10581 Issue ID: 10581 Summary: Mismatch of crypt() prototype on PPC Mac OS X 10.5.8, Leopard Product: OpenLDAP Version: 2.6.14 Hardware: Other OS: Mac OS Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: build Assignee: bugs(a)openldap.org Reporter: Peter_Dyballa(a)Web.DE Target Milestone: --- This happens with OpenLDAP versions 2.6.13 and 2.61.4: /opt/local/bin/gcc-mp-15 -pipe -Os -arch ppc -I../../include -I../../include -isystem/opt/local/include/LegacySupport -I/opt/local/include -I/opt/local/include/db48 -I/opt/local/include/openssl -DBIND_8_COMPAT -DMDB_FDATASYNC=fsync -DMDB_DSYNC=O_SYNC -c -o passwd.o passwd.c In file included from passwd.c:38: ../../include/ac/crypt.h:26:23: error: conflicting types for 'crypt'; have 'char *(void)' 26 | extern char *(crypt)(); | ^~~~~ In file included from /opt/local/include/LegacySupport/unistd.h:87, from ../../include/ac/unistd.h:25, from passwd.c:34: /usr/include/unistd.h:424:10: note: previous declaration of 'crypt' with type 'char *(const char *, const char *)' 424 | char *crypt(const char *, const char *); | ^~~~~ passwd.c: In function 'lutil_crypt': passwd.c:627:20: error: too many arguments to function 'crypt'; expected 0, have 2 627 | char *cr = crypt( key, salt ); | ^~~~~ ~~~ ../../include/ac/crypt.h:26:23: note: declared here 26 | extern char *(crypt)(); | ^~~~~ make[2]: *** [passwd.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/openldap-afe672a1/work/openldap-2.6.14/libraries/liblutil' make[1]: *** [all-common] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/openldap-afe672a1/work/openldap-2.6.14/libraries' make: *** [all-common] Error 1 make: Leaving directory `/opt/local/var/macports/build/openldap-afe672a1/work/openldap-2.6.14' Command failed: cd "/opt/local/var/macports/build/openldap-afe672a1/work/openldap-2.6.14" && /usr/bin/make -w all Exit code: 2 On Leopard /usr/include/unistd.h has: char *crypt(const char *, const char *); So I ended applying this simple patch: --- include/ac/crypt.h~ 2026-08-06 18:45:16.000000000 +0200 +++ include/ac/crypt.h 2026-08-30 11:21:21.000000000 +0200 @@ -22,8 +22,6 @@ /* crypt() may be defined in a separate include file */ #ifdef HAVE_CRYPT_H # include <crypt.h> -#else - extern char *(crypt)(); #endif #endif /* _AC_CRYPT_H */ This happens when using the MacPorts package manager. The issue can be viewed (and also commented) here: https://trac.macports.org/ticket/73673. -- You are receiving this mail because: You are on the CC list for the issue.

1 2

[Issue 10423] New: It is possible via cn=config to add an entry of one database type with the object class of another, causing OpenLDAP to crash
by openldap-its＠openldap.org 08 Sep '26

08 Sep '26

https://bugs.openldap.org/show_bug.cgi?id=10423 Issue ID: 10423 Summary: It is possible via cn=config to add an entry of one database type with the object class of another, causing OpenLDAP to crash Product: OpenLDAP Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: nivanova(a)symas.com Target Milestone: --- This happens specifically because the user by mistake attempts to create a meta database by specifying the object class for back-ldap. Since these share a lot of common attributes, schema checks do not fail. As a result, slapd initializes a meta database (based on olcDatabase value), but attempts to manipulate an initialized back-ldap database after that, and segfaults. Like this: dn: olcDatabase=meta,cn=config objectClass: olcDatabaseConfig objectClass: olcLDAPConfig olcDatabase: meta olcDbURI: "ldap://example.com" While it seems this is only possible for the proxy databases, we cannot rely that schema checks on attributes will fail for other database combinations, who knows what common attributes can be added or supplied in the future, we we have to fix this. The issue is reproducible via slapadd and at runtime with ldapadd. -- You are receiving this mail because: You are on the CC list for the issue.

1 7

[Issue 10580] Heap Use-After-Free in libldap During Concurrent Referral Completion and ldap_abandon_ext()
by openldap-its＠openldap.org 08 Sep '26

08 Sep '26

https://bugs.openldap.org/show_bug.cgi?id=10580 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Group|OpenLDAP-devs | -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 10282] New: MSVC builds are not supported
by openldap-its＠openldap.org 08 Sep '26

08 Sep '26

https://bugs.openldap.org/show_bug.cgi?id=10282 Issue ID: 10282 Summary: MSVC builds are not supported Product: OpenLDAP Version: 2.5.18 Hardware: All OS: Windows Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: build Assignee: bugs(a)openldap.org Reporter: cmb(a)php.net Target Milestone: --- I'm a maintainer of an OpenLDAP port[1] which is used to build liblber and libldap for PHP on Windows. So far this uses hand-made configuration and Visual Studio solutions, but that is not sustainable in the long run. Instead, I'd rather like to use the autotools based build chain with MSYS2 (or Cygwin), but still using the MSVC build tools (cl.exe, link.exe, etc.) and the MS Windows SDK for best compatibility with other builds for PHP on Windows. Apparently, this is not yet supported by OpenLDAP (2.5.18). I've managed to add some patches[2] to get where I'd like this to go[3]. Some of the patches are highly PHP (BC) specific, some are just quick hacks (because I don't know better), but some appear to be appropriate for inclusion into the OpenLDAP sources. Are you generally interested in supporting MSVC tools and MS Windows SDKs? If so, what would be the best way to contribute -- sending MRs to the repo[4]? Should these tackle individual issues, or rather be complete (note that I'm likely not able to provide a full-fledged solution due to my very limited knowledge of autotools and Linux, and limited time). [1] <https://github.com/winlibs/openldap> [2] <https://github.com/winlibs/openldap/tree/cmb/2.5.18> [3] <https://github.com/cmb69/winlib-builder/actions/runs/11713086509> [4] <https://git.openldap.org/openldap/openldap> -- You are receiving this mail because: You are on the CC list for the issue.

1 3

[Issue 10564] A single anonymous LDAP search with a crafted server-side-sort control heap-overflows the OpenLDAP slapd worker
by openldap-its＠openldap.org 20 Aug '26

20 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10564 --- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> --- head: • 4846d7e3 by Howard Chu at 2026-08-10T16:36:31+01:00 ITS#10564 slapo-sssvlv: tighten sss_parseCtrl RE27: • f92a2e17 by Howard Chu at 2026-08-20T21:02:57+00:00 ITS#10564 slapo-sssvlv: tighten sss_parseCtrl RE26: • 6c0323aa by Howard Chu at 2026-08-20T21:07:39+00:00 ITS#10564 slapo-sssvlv: tighten sss_parseCtrl -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 10575] New: MDB_WRITEMAP commit fails on Windows without MDB_NOSYNC on 1.0.1
by openldap-its＠openldap.org 20 Aug '26

20 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10575 Issue ID: 10575 Summary: MDB_WRITEMAP commit fails on Windows without MDB_NOSYNC on 1.0.1 Product: LMDB Version: 1.0.1 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: --- Created attachment 1194 --> https://bugs.openldap.org/attachment.cgi?id=1194&action=edit reproducer On Windows, an environment opened with MDB_WRITEMAP cannot commit a write transaction unless MDB_NOSYNC or MDB_NOMETASYNC is also set. mdb_txn_commit() fails with ERROR_INVALID_HANDLE. See attached for reproducer. This does not impact Linux, MacOS, or the .9.* series. -- You are receiving this mail because: You are on the CC list for the issue.

1 3

[Issue 10572] New: please add mdb_env_get_maxkeysize() to upgrading.doc for 1.0.x
by openldap-its＠openldap.org 20 Aug '26

20 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10572 Issue ID: 10572 Summary: please add mdb_env_get_maxkeysize() to upgrading.doc for 1.0.x Product: LMDB Version: 1.0.1 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: matthias.andree(a)gmx.de CC: steffen(a)sdaoden.eu Target Milestone: --- https://git.openldap.org/openldap/openldap/-/commit/136667a1492ea624b8d8bee… updated the mdb_env_get_maxkeysize() documentation for the LMDB_1.0.1 release such that it now correctly mentions it must be called after mdb_env_open() rather than mdb_env_create() (as was sufficient in 0.9.x), in response to a defect report from Steffen here https://bugs.openldap.org/show_bug.cgi?id=10534. Please add a relevant line that mdb_env_get_maxkeysize() can now (as of 1.0.0) only be called after mdb_env_open() to upgrading.doc so that LMDB users are aware they may need to move the mdb_env_get_maxkeysize() call in their code. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 10569] New: Makefile, lmdb.pc file show version 1.0.0
by openldap-its＠openldap.org 20 Aug '26

20 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=10569 Issue ID: 10569 Summary: Makefile, lmdb.pc file show version 1.0.0 Product: LMDB Version: 1.0.1 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: trivial Priority: --- Component: tools Assignee: bugs(a)openldap.org Reporter: hyc(a)openldap.org Target Milestone: --- The LMDB_VERSION in the Makefile wasn't updated. Makefile will be patched to obtain the version from the built binaries. -- You are receiving this mail because: You are on the CC list for the issue.

1 4

[Issue 9042] loglevel setting that allows seeing attribute values for MOD operations
by openldap-its＠openldap.org 19 Aug '26

19 Aug '26

https://bugs.openldap.org/show_bug.cgi?id=9042 Ondřej Kuzník <ondra(a)mistotebe.net> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.openldap.org/s | |how_bug.cgi?id=10576 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 10564] A single anonymous LDAP search with a crafted server-side-sort control heap-overflows the OpenLDAP slapd worker
by openldap-its＠openldap.org 18 Aug '26

18 Aug '26

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
2152
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs