https://bugs.openldap.org/show_bug.cgi?id=9741
Issue ID: 9741
Summary: Meaningless out-of-bound read in ldif-filter.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: matthias.st.pierre(a)ncp-e.com
Target Milestone: ---
I just stumbled over the following compiler warning in ldif-filter.c (see [1]):
14:10:41 ldif-filter.c:209:16: warning: adding 'int' to a string does not
append to the string [-Wstring-plus-int]
14:10:41 sep = "\r\n" + 2 - line_len; /* sep = copy(line)
*/
14:10:41 ~~~~~~~^~~
14:10:41 ldif-filter.c:209:16: note: use array indexing to silence this
warning
14:10:41 sep = "\r\n" + 2 - line_len; /* sep = copy(line)
*/
14:10:41 ^
14:10:41 & [ ]
While the expression is valid pointer arithmetic, it does not make sense to me,
because it calculates some (possibly negative) offset to the literal string
"\r\n" in memory, not the address of the beginning of some line, as the comment
`sep = copy(line)` suggests. (Originally added in commit [2]).
[1]
https://git.openldap.org/openldap/openldap/-/blob/master/tests/progs/ldif-f…
[2] https://git.openldap.org/openldap/openldap/-/commit/725743abdb
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9734
Issue ID: 9734
Summary: database ldap does not use SSL client certs as
configured
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: daniel(a)ylitalo.io
Target Milestone: ---
Created attachment 849
--> https://bugs.openldap.org/attachment.cgi?id=849&action=edit
Generated config
I'm trying to setup openldap to proxy against our account on ldap.google.com
with backend ldap but it does not seem like slapd uses the client cert and key
eventhough it's configured.
I'm receiving response "result: 50 Insufficient access" from local proxy/google
and the only way you can get that response is by not providing the client cert
and key.
I'm attaching the config used and the slapd.conf used to generate this config,
as you can see the olcDbStartTLS options are there in the ldif file but seems
not to be used.
(I've replaced our suffix with example.com)
The debug log entry is;
Nov 02 10:26:20 dev.example.com slapd[864482]:conn=1012 op=1 SRCH
base="dc=example,dc=com" scope=2 deref=0 filter="(uid=daniel.ylitalo)"
Nov 02 10:26:20 dev.example.com slapd[864482]: ==> limits_get: conn=1012 op=1
self="[anonymous]" this="dc=example,dc=com"
Nov 02 10:26:20 dev.example.com slapd[864482]: =>ldap_back_getconn: conn
0x7fb6101044b0 fetched refcnt=1.
Nov 02 10:26:20 dev.example.com slapd[864482]: => ldap_back_munge_filter
"(uid=daniel.ylitalo)"
Nov 02 10:26:20 dev.example.com slapd[864482]: <= ldap_back_munge_filter
"(uid=daniel.ylitalo)" (0)
Nov 02 10:26:20 dev.example.com slapd[864482]: conn=1012 op=1 ldap_back_retry:
retrying URI="ldaps://ldap.google.com:636" DN=""
Nov 02 10:26:20 dev.example.com slapd[864482]: => ldap_back_munge_filter
"(uid=daniel.ylitalo)"
Nov 02 10:26:20 dev.example.com slapd[864482]: <= ldap_back_munge_filter
"(uid=daniel.ylitalo)" (0)
Nov 02 10:26:20 dev.example.com slapd[864482]: send_ldap_result: conn=1012 op=1
p=3
Nov 02 10:26:20 dev.example.com slapd[864482]: send_ldap_result: err=50
matched="" text=""
Nov 02 10:26:20 dev.example.com slapd[864482]: send_ldap_response: msgid=2
tag=101 err=50
Nov 02 10:26:20 dev.example.com slapd[864482]: conn=1012 op=1 SEARCH RESULT
tag=101 err=50 nentries=0 text=
While using ldapsearch against same endpoint works just fine with the certs;
LDAPTLS_CERT=/etc/ldap/google.crt LDAPTLS_KEY=/etc/ldap/google.key ldapsearch
-H ldaps://ldap.google.com -b dc=example,dc=com '(uid=daniel.ylitalo)'
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9732
Issue ID: 9732
Summary: OpenLDAP TLS ciphersuite and groups limit issue
Product: OpenLDAP
Version: 2.4.54
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: narayananballem(a)gmail.com
Target Milestone: ---
Hi Team,
Hope you can help with this issue.
I am trying to disable SSLV3 on OpenLDAP servers we are using OpenLDAP as a
proxy with upstream Active directory servers. we are using CA certs on this
openssl we would like to disable SSLV3
I added the below entry slapd.conf but when I tried to start slapd it's failing
to start
TLSCipherSuite HIGH:MEDIUM:!SSLv2:!SSLV3
errors as below
slapd[19899]: main: TLS init def ctx failed: -1
slapd[19899]: slapd stopped.
slapd[19899]: connections_destroy: nothing to destroy.
debug logs restart as below
TLS: could not set cipher list HIGH:MEDIUM:!SSLv2:!SSLV3.
617c64c1 main: TLS init def ctx failed: -1
617c64c1 slapd stopped.
Also, did anybody notice this issue?
I am facing the issue with a group display we have several users in group while
looking for groups in getent group we are seeing a few groups not sure if there
is any limit on group filed in Database
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9002
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8226
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8226
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9002
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9715
Issue ID: 9715
Summary: Consolidate code for loglevel/logfile for better
shared usage between slapd and lloadd
Product: OpenLDAP
Version: unspecified
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 a future release, consolidate logging code, loglevel bits to be better
shared between slapd and stand-alone lloadd.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9723
Issue ID: 9723
Summary: C_EOF not reset in mdb_cursor_get with MDB_FIRST_DUP
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: stephan.j.bircher(a)gmail.com
Target Milestone: ---
I'm on the master branch of lmdb.
Steps to reproduce
// search for an non-existent key
rc = mdb_cursor_get(cursor, &key, &val, MDB_SET_RANGE);
if (rc == MDB_NOTFOUND) {
// C_EOF is not set on the cursor flags
// go to the last.
// C_EOF remains set which is ok
mdb_cursor_get(mdbCursor, &key, &val, MDB_LAST);
// go to the first dup of the last
// C_EOF remains set which is NOT OK
mdb_cursor_get(mdbCursor, &key, &val, MDB_FIRST_DUP);
// return MDB_NOTFOUND in any case whether there are duplicates or not
// because C_EOF was not cleared
mdb_cursor_get(mdbCursor, &key, &val, MDB_NEXT_NODUP);
}
Possible fix:
case MDB_FIRST_DUP:
mfunc = mdb_cursor_first;
mmove:
if (data == NULL || !(mc->mc_flags & C_INITIALIZED)) {
rc = EINVAL;
break;
}
if (mc->mc_xcursor == NULL) {
rc = MDB_INCOMPATIBLE;
break;
}
if (mc->mc_ki[mc->mc_top] >= NUMKEYS(mc->mc_pg[mc->mc_top])) {
mc->mc_ki[mc->mc_top] = NUMKEYS(mc->mc_pg[mc->mc_top]);
rc = MDB_NOTFOUND;
break;
}
{
MDB_node *leaf = NODEPTR(mc->mc_pg[mc->mc_top],
mc->mc_ki[mc->mc_top]);
if (!F_ISSET(leaf->mn_flags, F_DUPDATA)) {
MDB_GET_KEY(leaf, key);
rc = mdb_node_read(mc, leaf, data);
break;
}
}
if (!(mc->mc_xcursor->mx_cursor.mc_flags & C_INITIALIZED)) {
rc = EINVAL;
break;
}
rc = mfunc(&mc->mc_xcursor->mx_cursor, data, NULL);
// FIX: clear C_EOF
if (rc == MDB_SUCCESS && mc->mc_flags & C_EOF && mfunc ==
mdb_cursor_first) {
mc->mc_flags ^= C_EOF;
}
break;
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9492
Issue ID: 9492
Summary: Add local logging capa
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: mhardin(a)symas.com
Target Milestone: ---
Enhancement request: Add capability to slapd to log to a local file with log
rotation features. Log format should not change from syslog-generated log
style.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9641
Issue ID: 9641
Summary: accesslog when logging failed operations interferes
with deltasync
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: replication
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
Take delta-MPR setup and accesslog configured with logsuccess off. We encounter
a conflicting write (one that fails to apply in the DB) and fall back to plain
syncrepl. Since we are configured to log that write, syncprov sees it (it is a
failure, so doesn't match filter, which should contain reqResult=0) and sends a
LDAP_SYNC_NEW_COOKIE with that CSN to our delta-consumers. While we apply this
write locally in the fallback session, the consumers will skip what they see as
a duplicate and lose the change.
My understanding is that for failed operations, we should ignore the CSN we
received with the operation and instead set up a new one (with our own sid).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7215
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=9700
Issue ID: 9700
Summary: Need to determine new library ABI versioning starting
point
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
With the change in how OpenLDAP client libraries are versioned vs prior
releases, we need to determine a useful starting point for the current ABI
prior to release.
Since current libldap is versioned as libldap.so.2, we may want to start with
ol_api_current=2
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9157
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=8958
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8695
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9666
Issue ID: 9666
Summary: 2.5 to 2.6 upgrade documentation
Product: OpenLDAP
Version: unspecified
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: ---
Need to document any upgrade issues for going from 2.5 to 2.6
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8903
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6138
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9122
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9575
Issue ID: 9575
Summary: Object class olcGlobal should not allow
olcPasswordHash
Product: OpenLDAP
Version: 2.5.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
Object class olcGlobal should not allow olcPasswordHash because slapd will
crash during start if attribute is set.
Reported in this thread:
https://lists.openldap.org/hyperkitty/list/openldap-technical@openldap.org/…
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9713
Issue ID: 9713
Summary: slaptest fails to log failure reason when logfile is
not writeable
Product: OpenLDAP
Version: unspecified
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: ---
When using the logfile directive in slapd config. If the file exists, but is
not
writable by slaptest. The test fails, but there is no indication why:
/opt/OPENLDAP_REL_ENG_2_6/sbin/slaptest -v -u -f
/opt/install/slapd/opt/OPENLDAP_REL_ENG_2_6/etc/openldap/slapd.conf
slaptest: bad configuration file!
2.5.4 behaves differently. The test does not fail, regardless of whether the
file exists or not, or whether it is writable or not.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8333
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=6248
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|TEST |FIXED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8649
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |FIXED
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=9536
Issue ID: 9536
Summary: back-asyncmeta crashes when traffic is directed to a
new database, created via cn=config
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: nivanova(a)symas.com
Target Milestone: ---
A new back-asyncmeta database is successfully created via cn=config, but the
first LDAP request it tries to proxy causes a segmentation fault:
0# 0x00007F4C1E346629 in
/usr/src/backend/src/main/c++/overlay-proxy/.libs/overlay_proxy-2.4.so.0
1# 0x00007F4C26D701E0 in /lib64/libc.so.6
2# pthread_mutex_lock in /lib64/libpthread.so.0
3# ldap_pvt_thread_mutex_lock in /usr/local/libexec/slapd
4# asyncmeta_getconn in /usr/local/libexec/slapd
5# asyncmeta_back_add in /usr/local/libexec/slapd
6# fe_op_add in /usr/local/libexec/slapd
7# overlay_op_walk in /usr/local/libexec/slapd
8# 0x00000000004D8EFB in /usr/local/libexec/slapd
9# 0x00000000004D90DC in /usr/local/libexec/slapd
10# do_add in /usr/local/libexec/slapd
11# 0x0000000000445B20 in /usr/local/libexec/slapd
12# 0x00000000004460FB in /usr/local/libexec/slapd
13# 0x0000000000563C54 in /usr/local/libexec/slapd
14# 0x00007F4C270FB569 in /lib64/libpthread.so.0
15# clone in /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=9581
Issue ID: 9581
Summary: Add precision setting for slapd lastbind setting
Product: OpenLDAP
Version: 2.5.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The lastbind functionality that was imported into slapd for 2.5 is missing the
ability to fine tune the precision with which to allow the updates that was
present in the original overlay. It would be nice to have an option for it.
--
You are receiving this mail because:
You are on the CC list for the issue.