https://bugs.openldap.org/show_bug.cgi?id=9891
Issue ID: 9891
Summary: The test case execution time is too long.
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: 1010881517(a)qq.com
Target Milestone: ---
OpenLDAP test cases use a large amount of sleep. As a result, it takes a long
time to execute all test cases. Is there any way to shorten the time?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9896
Issue ID: 9896
Summary: Error: Could not locate TLS/SSL package
Product: OpenLDAP
Version: 2.5.13
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: vmaidarkar(a)gmail.com
Target Milestone: ---
Created attachment 909
--> https://bugs.openldap.org/attachment.cgi?id=909&action=edit
Error: Could not locate TLS/SSL package
Hi Team,
I'm getting the below error while installing OpenLDAP 2.5.13 on CentOS 7.9 &
OpenSSL 1.1.1g & attaching config.log file.
checking for openssl/ssl.h... yes
checking for SSL_export_keying_material_early in -lssl... no
configure: error: Could not locate TLS/SSL package
Kindly suggest how to fix this issue.
Thanks,
Vijay
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9893
Issue ID: 9893
Summary: Unable to create ldap object with same unique value as
deleted object
Product: OpenLDAP
Version: 2.6.3
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: curtis.ruck+github(a)gmail.com
Target Milestone: ---
I have a unique overlay that is trying to ensure uniqueness of two attributes,
mail and uid.
My configdir config for my mdb database:
dn: olcOverlay={1}unique
objectClass: olcUniqueConfig
objectClass: olcOverlayConfig
olcOverlay: unique
olcUniqueURI: ldap://?mail?sub
olcUniqueURI: ldap://?uid?sub
structuralObjectClass: olcUniqueConfig
If I delete a user, and then go to recreate it, I get this error:
msgtype 105, error 19, constraint violation
non-unique attributes found with (|(uid=jdoe)(givenName=John)(sn=Doe)(cn=John
Doe)(mail=john(a)example.com)(userPassword=<password>)(objectClass=inetOrgPerson))
Somehow I believe the unique index structure is broken.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9890
Issue ID: 9890
Summary: Core is seen while reboot for RHEL_8_4_X86_64
Product: OpenLDAP
Version: 2.4.59
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: sunil.ece.126(a)gmail.com
Target Milestone: ---
Hi,
I am seeing below core while using openLdap 2.4.59. We are using openLdap in
our application as stack to initiate the connection towards ldapServer.
Current I am using RHEL_8_4_X86_64.
Core is seen whenever system is going for reboot.
Let me know if more information is required.
(gdb) bt
#0 0x00007ff94be7d998 in vtable for {}cxxabiv1::{_}_si_class_type_info () from
/lib64/libstdc++.so.6
#1 0x00007ff9520296cc in ManagedObjectList*
ManagedObject::findMOListByKey<MOID>(MOID const&) const ()
from /usr/IMS/current/bin/libMX.so.0
#2 0x00007ff9520287a5 in ManagedObject::findObjectById(MOID const&) const ()
from /usr/IMS/current/bin/libMX.so.0
#3 0x00007ff952029fa9 in SignalInstaller::signalAction(int, siginfo_t*, void*)
() from /usr/IMS/current/bin/libMX.so.0
#4 <signal handler called>
#5 memfence_check (ptr=0x7fffffff00000000, size=0x0) at src/tcmalloc.cc:294
#6 0x00007ff94c72f90d in memfence_check_and_free (ptr=<optimized out>,
size=size@entry=0x0) at src/tcmalloc.cc:307
#7 0x00007ff94c73dfe4 in free_fast_path (ptr=<optimized out>) at
src/tcmalloc.cc:2142
#8 tc_free (ptr=<optimized out>) at src/tcmalloc.cc:2149
#9 0x00007ff949d3b0ce in ldap_int_destroy_global_options () from
/lib64/libldap-2.4.so.2
#10 0x00007ff9528cfc96 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#11 0x00007ff94b1d0b0c in __run_exit_handlers () from /lib64/libc.so.6
#12 0x00007ff94b1d0c40 in exit () from /lib64/libc.so.6
#13 0x00007ff94b1ba49a in __libc_start_main () from /lib64/libc.so.6
#14 0x0000000000427b6e in _start ()
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9885
Issue ID: 9885
Summary: Error while compilation of Openldap 2.5.9
Product: OpenLDAP
Version: 2.5.9
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: rekha.shivsan(a)gmail.com
Target Milestone: ---
Created attachment 908
--> https://bugs.openldap.org/attachment.cgi?id=908&action=edit
Error while compilation
Hi,
We are trying to install Openldap v2.5.9. While running the make command we are
seeing below error.
./.libs/libldap.so: undefined reference to `BIO_meth_set_read'
./.libs/libldap.so: undefined reference to `BIO_get_data'
./.libs/libldap.so: undefined reference to `BIO_meth_set_write'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_value'
./.libs/libldap.so: undefined reference to `BIO_meth_set_ctrl'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_new_null'
./.libs/libldap.so: undefined reference to `BIO_meth_set_gets'
./.libs/libldap.so: undefined reference to `BIO_meth_set_create'
./.libs/libldap.so: undefined reference to `SSL_CTX_set_ciphersuites'
./.libs/libldap.so: undefined reference to `BIO_meth_set_puts'
./.libs/libldap.so: undefined reference to `BIO_meth_free'
./.libs/libldap.so: undefined reference to `BIO_meth_new'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_push'
./.libs/libldap.so: undefined reference to `EVP_MD_CTX_new'
./.libs/libldap.so: undefined reference to `X509_NAME_get0_der'
./.libs/libldap.so: undefined reference to `BIO_set_init'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_num'
./.libs/libldap.so: undefined reference to `SSL_CTX_up_ref'
./.libs/libldap.so: undefined reference to `OPENSSL_init_ssl'
./.libs/libldap.so: undefined reference to `ASN1_STRING_get0_data'
./.libs/libldap.so: undefined reference to `TLS_method'
./.libs/libldap.so: undefined reference to `EVP_MD_CTX_free'
./.libs/libldap.so: undefined reference to `SSL_CTX_set_options'
./.libs/libldap.so: undefined reference to `SSL_set_ciphersuites'
./.libs/libldap.so: undefined reference to `BIO_meth_set_destroy'
./.libs/libldap.so: undefined reference to `SSL_session_reused'
./.libs/libldap.so: undefined reference to `X509_get_X509_PUBKEY'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_free'
./.libs/libldap.so: undefined reference to `BIO_set_data'
./.libs/libldap.so: undefined reference to `SSL_CTX_clear_options'
collect2: error: ld returned 1 exit status
Complete error logs are attached " OpenLdap 2.5.9_error.txt".
Could you please help to resolve this issue.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9873
Issue ID: 9873
Summary: idle timeout by backends close connections
Product: OpenLDAP
Version: 2.6.2
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ettorevi(a)gmail.com
Target Milestone: ---
Hi,
making searches through lloadd to a bunch of backends returns weird results
Sometimes I get:
| ldap_bind: Other (e.g., implementation specific) error (80)
| additional info: connection to the remote server has been severed
Others
ldap_result: Can't contact LDAP server (-1)
due to an idle_timeout from the backend in the middle of the search, in a non
deterministic way.
If I search directly on the backends everything works
ldapsearch -x -Hldaps://lloadd.server 'objectClass=*' -w pwd
[...]
# numResponses: 9620
# numEntries: 9620
ldap_result: Can't contact LDAP server (-1)
lloadd compiled standalone from 2.6.2 with:
--enable-balancer=yes --enable-syslog --enable-debug --enable-slapd=no
Backends are older, 2.4.49+dfsg-2ubuntu1.9 from Ubuntu 20.04
Any hints?
Thank you
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9846
Issue ID: 9846
Summary: Provide ppm v2.2
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: contrib
Assignee: bugs(a)openldap.org
Reporter: david.coutadeur(a)gmail.com
Target Milestone: ---
Provide the new release of ppm: v2.2:
- implement a maximum number of characters for each class #18
- upgrade documentation for new olcPPolicyCheckModule in OpenLDAP 2.6 #30
- Make one unique code of development for 2.5 and 2.6 OpenLDAP versions #35
- fix segmentation fault in ppm_test #36
- various minor fixes and optimizations
See: https://github.com/ltb-project/ppm/milestone/5
I am going to propose a MR soon.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9856
Issue ID: 9856
Summary: Lloadd doesn't tag Notice of Disconnection
responseName
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
The responseName field in Notice of Disconnection is being tagged as a generic
octet string, where RFC4511 marks it with "responseValue [11] OCTET STRING
OPTIONAL". 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=9858
Issue ID: 9858
Summary: cn=config replication refresh breaks mdb database
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
working in an environment with the following layout:
Config node -> This node contains the cn=config databases for consumers in one
tree and providers in another tree.
provider nodes -> Pull their configuration from the config node via standard
syncrepl
consumer nodes -> Pull their configuration from the config node via standard
syncrepl
This worked fine with OpenLDAP 2.4.
With 2.6, using the same cn=config configuration, slapd will segfault if the
cn=config db is put through a REFRESH sequence. I've ruled out syncprov as an
issue as I removed the syncprov configuration from the consumer nodes entirely
and it still occurs (I was thinking perhaps it was the syncprov checkpoint at
shutdown). At this point I can reproduce this trivially 100% of the time
simply by having a node REFRESH cn=config.
Once the REFRESH has occurred, slapd will continue running. However the next
time it is stopped/started it will SEGV on startup. It is usually possible to
use slapcat to extract the MDB database and rebuild it, at which point slapd
will start again. A couple of times I was only able to extract a portion of
the database using slapcat (70MB of 650MB).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9855
Issue ID: 9855
Summary: Implement a module to enable case-insensitive Boolean
values
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: contrib
Assignee: bugs(a)openldap.org
Reporter: nivanova(a)symas.com
Target Milestone: ---
The module, when loaded from slapd.conf, will allow for values such as true,
false and True, False, to be accepted by the server
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9850
Issue ID: 9850
Summary: slapd-watcher ignores sids when only 1 server is
specified
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When only 1 URL is provided, it always uses only a contextCSN with sid=0.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9865
Issue ID: 9865
Summary: slapd-watcher: support for glue
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: enhancement
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When operating on glued backends, the DB where entry counts need to be
monitored may be different from where the contextCSN updates occur. Add a "-c"
option to allow specifying the contextCSN baseDN, separate from the main "-b"
baseDN.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9872
Issue ID: 9872
Summary: slapd-ldap(5) man page missing bold tag on authz
parameter
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The slapd-ldap(5) man page is missing a bold tag on the authz configuration
parameter.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9864
Issue ID: 9864
Summary: One-time leaks in accesslog
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: minor
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
In tool mode, the accesslog's configured logdb suffix isn't freed. It's
normally freed by the db_open handler but in tool mode the overlay never
actually gets opened.
Also due to 414866b8889 ITS#9580, li_sids can leak when replacing mincsn.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8882
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9867
Issue ID: 9867
Summary: syncprov leak on early Abandons
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
The baseDN found by syncprov_findbase() can be leaked if an Abandon or error
occurs early during psearch processing.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9871
Issue ID: 9871
Summary: bind operations on relay entries cause slapd to
segfault with rwm and ppolicy enabled
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: subbarao(a)computer.org
Target Milestone: ---
On 2.5.12, slapd crashes during bind operations on relay entries with rwm and
ppolicy both enabled. A simple way to reproduce this issue is to edit
tests/scripts/relay and tests/data/slapd-relay.conf as follows, and then run
test030-relay. I think this issue is the same as ITS#7966 reported in 2014.
--- tests/scripts/relay.orig 2022-05-04 07:57:30.000000000 -0700
+++ tests/scripts/relay 2022-06-23 17:16:42.020652093 -0700
@@ -356,6 +356,16 @@
exit 1
fi
+$LDAPADD -D "$MANAGERDN" -H $URI1 -w $PASSWD <<EOF > /dev/null 2>&1
+dn: cn=ppolicy,dc=example,dc=com
+objectClass: top
+objectClass: device
+objectClass: pwdPolicy
+cn: ppolicy
+pwdMinLength: 5
+pwdAttribute: userPassword
+EOF
+
BASEDN="o=Example,c=US"
echo "Changing password to database \"$BASEDN\"..."
$LDAPPASSWD -H $URI1 -D "cn=Manager,$BASEDN" -w $PASSWD \
--- tests/data/slapd-relay.conf.orig 2022-05-04 07:57:30.000000000 -0700
+++ tests/data/slapd-relay.conf 2022-06-23 16:57:15.184456120 -0700
@@ -31,6 +31,8 @@
#metamod#moduleload back_meta.la
#rwmmod#modulepath ../servers/slapd/overlays/
#rwmmod#moduleload rwm.la
+#ppolicymod#modulepath ../servers/slapd/overlays/
+#ppolicymod#moduleload ppolicy.la
#######################################################################
# database definitions
@@ -46,6 +48,9 @@
#ndb#dbname db_1
#ndb#include @DATADIR@/ndb.conf
+overlay ppolicy
+ppolicy_default cn=ppolicy,dc=example,dc=com
+
database @RELAY@
suffix "o=Example,c=US"
### back-relay can automatically instantiate the rwm overlay
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9876
Issue ID: 9876
Summary: Coverity report on OpenLDAP libraries and client tools
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: simon.pichugin(a)gmail.com
Target Milestone: ---
Created attachment 906
--> https://bugs.openldap.org/attachment.cgi?id=906&action=edit
Covscan report for OpenLDAP 2.6.2
I've got a report from our Coverity Scan system. It had a lot of false
positives so I've filtered it a bit.
Please, find below the report with only RESOURCE_LEAK, LOCK, and MISSING_LOCK
issues.
I think there are still some false positives left, but I hope it's worth
checking by core OpenLDAP developers.
The report:
https://spichugi.fedorapeople.org/openldap-covscan-2.6.2.html
Thank you!
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9866
Issue ID: 9866
Summary: delta-sync memleak on Adds
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Due to the entry->e_name massaging in back-mdb/add.c (ITS#5326) syncrepl wasn't
freeing the non-normalized DN as expected after add finished.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9840
Issue ID: 9840
Summary: Fix parallel build failures
Product: OpenLDAP
Version: 2.5.9
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: yi.zhao(a)windriver.com
Target Milestone: ---
Created attachment 899
--> https://bugs.openldap.org/attachment.cgi?id=899&action=edit
0001-ldif-filter-fix-parallel-build-failure.patch
I found there are two parallel build errors for ldif-filter and libraries:
ldif-filter:
ld: cannot find slapd-common.o: No such file or directory
libraries:
../../build/shtool mkdir -p
TOPDIR/tmp-glibc/work/cortexa15t2hf-neon-wrs-linux-gnueabi/openldap/2.5.9-r0/image/usr/lib
mkdir: cannot create directory
'TOPDIR/tmp-glibc/work/cortexa15t2hf-neon-wrs-linux-gnueabi/openldap/2.5.9-r0/image/usr/lib':
File exists
make[1]: *** [Makefile:288: install-local] Error 1
I have attached 2 patches to fix these issues.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9824
Issue ID: 9824
Summary: getting/setting LDAP_OPT_X_SASL_ options require call
to ldap_initialize
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: jay.hendren(a)colorado.edu
Target Milestone: ---
Originally filed against python-ldap:
https://github.com/python-ldap/python-ldap/issues/468
Per "man 3 ldap_get_option", some options can be set globally while others
require an initialized LDAP struct:
> These routines provide access to options stored either in a LDAP handle or as global options, where applicable.
However, "where applicable" doesn't seem to have any further clarification. In
particular, getting or setting any of the "LDAP_OPT_X_SASL_" options appears to
require an initialized LDAP struct, as noted in the bug report against
python-ldap, whereas most other options do not appear to share this
requirement. I cannot find this fact documented anywhere.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9841
Issue ID: 9841
Summary: Build failure on musl due to conflicting declarations
of ber_calloc
Product: OpenLDAP
Version: 2.5.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: helmut(a)subdivi.de
Target Milestone: ---
This is a forward of a Debian bug at https://bugs.debian.org/1008951 and a
Gentoo bug at https://bugs.gentoo.org/546556.
In essence, openldap #defines calloc ber_calloc and then #includes some system
headers, which happen to #include <sched.h>. musl's <sched.h> happens to
delcare calloc when _GNU_SOURCE is #defined. Since this is the case, musl's
declaration is diverted to ber_calloc and since one parameter has a subtly
different type, the declarations cause a conflict.
I think this is actually two bugs.
1. musl should not declare calloc in <sched.h>. Doing so also breaks libgccjit
(citation needed).
2. openldap should not #define calloc before #including system headers.
Fixing either fixes the build failure. I think we should fix both.
The openldap side can be fixed by reordering the #define and the relevant
#include. You can find a working patch in the Debian bug above at
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1008951;filename=mu….
Does this look acceptable for inclusion into openldap?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9882
Issue ID: 9882
Summary: slapd crashes when lastbind enabled w/ multi-provider
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: smckinney(a)symas.com
Target Milestone: ---
Created attachment 907
--> https://bugs.openldap.org/attachment.cgi?id=907&action=edit
slapd.conf
Description:
Crash during bind operation when lastbind's enabled in a multi-provider env.
Built from source:
commit 23ef018c6f321413141f26ed6e1909f85047ba76 (HEAD -> OPENLDAP_REL_ENG_2_6,
origin/OPENLDAP_REL_ENG_2_6)
Configuration: attached
System: AlmaLinux8
Backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000000004dfe66 in over_op_func (op=0x7d6b1fffe690, rs=0x7d6b1fffe620,
which=op_modify) at backover.c:749
749 on = oi->oi_list;
[Current thread is 1 (Thread 0x7d6b1ffff700 (LWP 96272))]
Missing separate debuginfos, use: yum debuginfo-install
cyrus-sasl-lib-2.1.27-6.el8_5.x86_64 glibc-2.28-189.5.el8_6.x86_64
keyutils-libs-1.5.10-9.el8.x86_64 krb5-libs-1.18.2-14.el8.x86_64
libblkid-2.32.1-35.el8.x86_64 libcap-2.48-2.el8.x86_64
libcom_err-1.45.6-4.el8.x86_64 libdb-5.3.28-42.el8_4.x86_64
libgcc-8.5.0-10.1.el8_6.alma.x86_64 libmount-2.32.1-35.el8.x86_64
libselinux-2.9-5.el8.x86_64 libtool-ltdl-2.4.6-25.el8.x86_64
libuuid-2.32.1-35.el8.x86_64 libxcrypt-4.1.1-6.el8.x86_64
openssl-libs-1.1.1k-6.el8_5.x86_64 pcre2-10.32-2.el8.x86_64
systemd-libs-239-58.el8.x86_64 zlib-1.2.11-18.el8_5.x86_64
(gdb) bt
#0 0x00000000004dfe66 in over_op_func (op=0x7d6b1fffe690, rs=0x7d6b1fffe620,
which=op_modify) at backover.c:749
#1 0x00000000004e0135 in over_op_modify (op=0x7d6b1fffe690, rs=0x7d6b1fffe620)
at backover.c:808
#2 0x000000000046d785 in fe_op_lastbind (op=0x7d6b1010ed40) at bind.c:503
#3 0x000000000046da7f in fe_op_bind_success (op=0x7d6b1010ed40,
rs=0x7d6b1fffe960) at bind.c:548
#4 0x000000000046d1e1 in fe_op_bind (op=0x7d6b1010ed40, rs=0x7d6b1fffe960) at
bind.c:386
#5 0x000000000046c8cd in do_bind (op=0x7d6b1010ed40, rs=0x7d6b1fffe960) at
bind.c:206
#6 0x000000000044427d in connection_operation (ctx=0x7d6b1fffea90,
arg_v=0x7d6b1010ed40) at connection.c:1115
#7 0x000000000044488f in connection_read_thread (ctx=0x7d6b1fffea90,
argv=0x16) at connection.c:1267
#8 0x00007f5f2d60a470 in ldap_int_thread_pool_wrapper (xpool=0xc79d80) at
tpool.c:1053
#9 0x00007f5f2c1a51cf in start_thread () from /lib64/libpthread.so.0
#10 0x00007f5f2be11dd3 in clone () from /lib64/libc.so.6
--
You are receiving this mail because:
You are on the CC list for the issue.