https://bugs.openldap.org/show_bug.cgi?id=10059
Issue ID: 10059
Summary: slapo-homedir(5) could benefit from an configuration
example
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: craig.balfour(a)gmail.com
Target Milestone: ---
Created attachment 967
--> https://bugs.openldap.org/attachment.cgi?id=967&action=edit
Patch
This module could do with an example of how to configure it.
Patch attached.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10101
Issue ID: 10101
Summary: Fix double file close when first TLS connection fails
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: florin.crisan(a)axigen.com
Target Milestone: ---
Created attachment 981
--> https://bugs.openldap.org/attachment.cgi?id=981&action=edit
Proof of concept
1. ldap_initialize a connection with multiple URLs, the first one being
LDAPS. (For example: "ldaps://server,ldap://server").
The LDAPS connection needs to successfully open the TCP connection,
but fail during TLS negotiation.
2. When TLS negotiation fails, ldap_int_open_connection calls
ber_int_sb_close (which closes the connections attached to the sockbuf)
but fails to call ber_int_sb_destroy, so the TCP layers are still attached
to the sockbuf structure.
3. When the second connection is opened, a new TCP layer is added to the
sockbuf structure, but the existing one is still there. Both now point to
the updated sockbuf structure, with the new file descriptor.
4. When the connection is closed, the layers attached to the sockbuf close
the new file descriptor twice.
This may be the same problem as
https://lists.openldap.org/hyperkitty/list/openldap-devel@openldap.org/thre…
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10153
Issue ID: 10153
Summary: slapd(8) manpage does not describe -T modify
(slapmodify)
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: fumiyas(a)osstech.co.jp
Target Milestone: ---
Created attachment 998
--> https://bugs.openldap.org/attachment.cgi?id=998&action=edit
[PATCH] slapd(8) describe -T modify (slapmodify)
OpenLDAP 2.5+ slapd(8) add `-T modify` option, but its manpage does not
describe it.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10123
Issue ID: 10123
Summary: Allow compilation with new compilers
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
With clang 16 at least, slapd fails to compile servers/slapd/controls.c
(missing an include of ac/ctype.h) and emits a large amount of warnings
stemming from include/ac/* redefining existing functions in a K&R way (which
apparently is not compatible with C2x).
A fix is coming.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10109
Issue ID: 10109
Summary: [slapd] Segmentation fault
Product: OpenLDAP
Version: 2.6.6
Hardware: x86_64
OS: Windows
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: sfhacker(a)hotmail.com
Target Milestone: ---
Created attachment 984
--> https://bugs.openldap.org/attachment.cgi?id=984&action=edit
Backtrace
Hi.
OpenLDAP 2.6.6 built from source on Windows 10 x64.
When starting the server using a basic slapd.conf file, I get a segmentation
fault (see screenshot attached).
Thanks in advance.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10110
Issue ID: 10110
Summary: Chained searches skip callbacks for returned entries
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
Regardless of overlay ordering, slapo-chain's handling of entries returned will
skip any callbacks that have been registered on the operation.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10076
Issue ID: 10076
Summary: suffixmassage in back-asyncmeta does not handle empty
remote suffix correctly
Product: OpenLDAP
Version: 2.6.4
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: nivanova(a)symas.com
Target Milestone: ---
When configuring a suffixmassage directive on an asyncmeta database,
a configuration like:
suffixmassage "dc=example,dc=com" ""
causes search requests to return error 34 "Invalid DN", because the empty
remote suffix is massaged incorrectly, adding an unnecessary ",".
The issue applies only to asyncmeta, on other proxies it functions correctly.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10139
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Group|OpenLDAP-devs |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7420
--- Comment #11 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
commit d56dcccb6f6cfd590eb20628eec39ab815a65f5a
Author: Howard Chu <hyc(a)openldap.org>
Date: Sun Jan 28 04:43:44 2024 +0000
ITS#7420 clarify prev commit
commit 03338946b3e165e3c703c57cede266c42418cc1f
Author: Howard Chu <hyc(a)openldap.org>
Date: Sun Jan 28 04:00:34 2024 +0000
ITS#7420 more for prev commit
On naming error, don't free modvals
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8618
--- Comment #28 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #27)
> (In reply to Quanah Gibson-Mount from comment #26)
> > Additionally, this was clearly documented in the UPGRADE section of the Admin guide.
>
> Specifically, in the OpenLDAP 2.5 admin guide section on upgrading from
> OpenLDAP 2.4 or prior releases.
https://www.openldap.org/doc/admin25/appendix-upgrading.html#Client%20utili…
--
You are receiving this mail because:
You are on the CC list for the issue.