https://bugs.openldap.org/show_bug.cgi?id=10047
Issue ID: 10047
Summary: slapd SEGV after slapindex -q
Product: OpenLDAP
Version: 2.6.3
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: ---
In an environment where cn=config is replicated:
a) Added an equality index for an existing attribute
b) Stopped slapd after the change to the configuration had been replicated to
the server. The indexing process that was automatically kicked off by this had
been running for ~30 minutes before I stopped slapd
c) ran: slapindex -q -F /path/to/config -b <base> <attr>
d) started slapd
e) segfault
To verify it wasn't an overall data issue, I then:
a) slapcat the database
b) moved the problem database files aside for debugging
c) reloaded the database with slapadd -q
d) everything works fine
I will attach the gdb output to this ticket momentarily
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10042
Issue ID: 10042
Summary: Crash when back-monitor search fails/is abandoned
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
The fix in ITS#9832 was incomplete, some paths leading to "freeout:" can have
passed through monitor_cache_release already.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9993
Issue ID: 9993
Summary: Potential race condition in back-mdb online indexer
Product: OpenLDAP
Version: 2.5.13
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When the online indexer completes, it should mutex-protect its resetting of the
indexing flags.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10039
Issue ID: 10039
Summary: configure fails to detect
SSL_export_keying_material_early with LibreSSL
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: orbea(a)riseup.net
Target Milestone: ---
Created attachment 957
--> https://bugs.openldap.org/attachment.cgi?id=957&action=edit
config.log
When configuring OpenLDAP using --with-tls=openssl with LibreSSL the configure
will fail to detect SSL_export_keying_material_early since LibreSSL doesn't
support this function yet. However OpenLDAP doesn't actually use this function
so this can be easily solved by checking for SSL_library_init which is a more
standard function which both OpenSSL and LibreSSL support which OpenLDAP
actually uses in libraries/libldap/tls_o.c.
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... yes
checking for openssl/ssl.h... yes
checking for SSL_export_keying_material_early in -lssl... no
configure: error: Could not locate TLS/SSL package
Other than this the build succeeds correctly with at least LibreSSL 3.7.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9995
Issue ID: 9995
Summary: Potential memory leak in clients/tools/ldapdelete.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: 1061499390(a)qq.com
Target Milestone: ---
Version: Github:master
Potential memory leak in ldapdelete.c line 384.Calling ldap_search_ext_s()
without calling ldap_msgfree() to free the memory will cause a memory leak.
Doc says "Note that res parameter of ldap_search_ext_s() and
ldap_search_s() should be freed with ldap_msgfree() regardless of return value
of these functions." in
https://www.openldap.org/software/man.cgi?query=ldap_search_ext_s&apropos=0…
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10032
Issue ID: 10032
Summary: at_add returns a free'd pointer on error
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
When an invalid schema is provided (e.g. the current
./servers/slapd/schema/msuser.schema of memberof/dynlist is loaded already),
at_add() hits error handling and frees at->at_oid, but that string is being
returned in *err. 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=9989
Issue ID: 9989
Summary: «make clean» shall not delete
libraries/libldap/ldap.pc and
libraries/liblber/lber.pc
Product: OpenLDAP
Version: 2.6.3
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
«./configure» and «./config.status» do create ./libraries/libldap/ldap.pc,
./libraries/liblber/lber.pc, while «make clean» deletes both .pc files.
«make install» fails, if ./libraries/libldap/ldap.pc or
./libraries/liblber/lber.pc are missing.
«./configure && make clean && make depend && make install» is a valid workflow
for many other (autoconf/automake based) projects.
./libraries/libldap/ldap.pc and ./libraries/liblber/lber.pc shall be deleted by
«make distclean», and kept by «make clean».
See also https://www.gnu.org/prep/standards/html_node/Standard-Targets.html for
the idea behind «make clean» vs «make distclean».
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10028
Issue ID: 10028
Summary: crash with pwdMinDelay
Product: OpenLDAP
Version: 2.5.14
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hamano(a)osstech.co.jp
Target Milestone: ---
slapd crash when using pwdMinDelay of ppolicy.
The cause is that slap_timestamp() writes to undefined area.
It has already been fixed.
backtrace:
```
(gdb) bt
#0 0x00007f2c70bdbaff in raise () from /lib64/libc.so.6
#1 0x00007f2c70baeea5 in abort () from /lib64/libc.so.6
#2 0x00007f2c70baed79 in __assert_fail_base.cold.0 () from /lib64/libc.so.6
#3 0x00007f2c70bd4456 in __assert_fail () from /lib64/libc.so.6
#4 0x0000000000499fdf in entry_schema_check (op=<optimized out>,
op@entry=0x7f2c2a9a9ff0,
e=<optimized out>, e@entry=0x7f2c20001d30, oldattrs=<optimized out>,
oldattrs@entry=0x7f2c20001d30, manage=0, add=add@entry=0,
socp=socp@entry=0x7f2c2a9a99d8,
text=0x7f2c2a9a9f30, textbuf=0x7f2c2a9a9b40 "", textlen=256)
at ../../../servers/slapd/schema_check.c:89
#5 0x00000000004f5dc1 in mdb_modify_internal (op=<optimized out>,
op@entry=0x7f2c2a9a9ff0,
tid=tid@entry=0x11dc8c0, modlist=<optimized out>, e=<optimized out>,
e@entry=0x7f2c2a9a9ac0,
text=text@entry=0x7f2c2a9a9f30, textbuf=textbuf@entry=0x7f2c2a9a9b40 "",
textlen=256)
at ../../../../servers/slapd/back-mdb/modify.c:419
#6 0x00000000004f6cfa in mdb_modify (op=0x7f2c2a9a9ff0, rs=0x7f2c2a9a9f10)
at ../../../../servers/slapd/back-mdb/modify.c:714
#7 0x00000000004d5833 in overlay_op_walk (op=0x7f2c2a9a9ff0,
rs=0x7f2c2a9a9f10,
which=<optimized out>, oi=0xfc1a00, on=0x0) at
../../../servers/slapd/backover.c:706
#8 over_op_func (op=0x7f2c2a9a9ff0, rs=0x7f2c2a9a9f10, which=op_modify)
at ../../../servers/slapd/backover.c:766
#9 0x00007f2c6be56a95 in ppolicy_bind_response (op=<optimized out>,
rs=0x7f2c2a9aa730)
at ../../../../servers/slapd/overlays/ppolicy.c:1827
#10 0x0000000000475878 in slap_response_play (op=0x7f2c201039a0,
rs=0x7f2c2a9aa730)
at ../../../servers/slapd/result.c:567
#11 send_ldap_response (op=op@entry=0x7f2c201039a0, rs=rs@entry=0x7f2c2a9aa730)
at ../../../servers/slapd/result.c:642
#12 0x0000000000475f2c in slap_send_ldap_result (op=0x7f2c201039a0,
rs=0x7f2c2a9aa730)
at ../../../servers/slapd/result.c:918
#13 0x000000000052b6cf in mdb_bind (op=0x7f2c201039a0, rs=0x7f2c2a9aa730)
at ../../../../servers/slapd/back-mdb/bind.c:148
#14 0x00000000004d5833 in overlay_op_walk (op=0x7f2c201039a0,
rs=0x7f2c2a9aa730,
which=<optimized out>, oi=0xfc1a00, on=0x0) at
../../../servers/slapd/backover.c:706
#15 over_op_func (op=0x7f2c201039a0, rs=0x7f2c2a9aa730, which=op_bind)
at ../../../servers/slapd/backover.c:766
#16 0x00000000004824f2 in fe_op_bind (op=0x7f2c201039a0, rs=0x7f2c2a9aa730)
at ../../../servers/slapd/bind.c:383
#17 0x00000000004822ea in do_bind (op=0x7f2c201039a0, rs=0x7f2c2a9aa730)
at ../../../servers/slapd/bind.c:206
#18 0x0000000000466847 in connection_operation (ctx=<optimized out>,
ctx@entry=0x7f2c2a9aa9b8,
arg_v=arg_v@entry=0x7f2c201039a0) at
../../../servers/slapd/connection.c:1113
#19 0x0000000000465ec1 in connection_read_thread (ctx=<optimized out>,
argv=0x11)
at ../../../servers/slapd/connection.c:1265
#20 0x00007f2c72d5ea22 in ldap_int_thread_pool_wrapper (xpool=<optimized out>)
at ../../../libraries/libldap/tpool.c:1053
#21 0x00007f2c70f5b1cf in start_thread () from /lib64/libpthread.so.0
#22 0x00007f2c70bc6e73 in clone () from /lib64/libc.so.6
```
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9997
Issue ID: 9997
Summary: Potential memory leak in servers/slapd/syncrepl.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: 1061499390(a)qq.com
Target Milestone: ---
Version: Github:master
Potential memory leak in syncrepl.c line 605.Calling ldap_search_ext_s()
without calling ldap_msgfree() to free the memory will cause a memory leak.
Doc says "Note that res parameter of ldap_search_ext_s() and
ldap_search_s() should be freed with ldap_msgfree() regardless of return value
of these functions." in
https://www.openldap.org/software/man.cgi?query=ldap_search_ext_s&apropos=0…
--
You are receiving this mail because:
You are on the CC list for the issue.