https://bugs.openldap.org/show_bug.cgi?id=9286
Issue ID: 9286
Summary: mdb_cursor_get MDB_GET_MULTIPLE key not populated
Product: LMDB
Version: 0.9.25
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: corey(a)kaylors.net
Target Milestone: ---
Reading the docs it says "Return key and up to a page of duplicate data items
from current cursor position." when MDB_GET_MULTIPLE is used. I don't see the
key being populated, but when I call MDB_GET_CURRENT after the use of
MDB_GET_MULTIPLE the key is the value I expect. Looking through the code I
don't see the key getting used in this path. Granted, I'm not proficient with C
so I may have overlooked something.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9268
Issue ID: 9268
Summary: Test065 fails due to invalid log level
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: andy(a)asjohnson.com
Target Milestone: ---
Line #109 of tests/scripts/test065-proxyauthz:
$SLAPD -f $CONF2 -h $URI2 -d $LVL -d pcache > $LOG2 2>&1 &
Results in this:
must compile with LDAP_DEBUG for debugging
unrecognized log level "pcache" (deferred)
After which the test fails.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9250
Bug ID: 9250
Summary: librewrite only supports up to 9 submatches
Product: OpenLDAP
Version: 2.4.49
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
libraries/librewrite$ cat nine.conf
rewriteEngine on
rewriteContext default
rewriteRule "(.)(.)(.)(.)(.)(.)(.)(.)(.)" "$9$8$7$6$5$4$3$2$1" :
libraries/librewrite$ ./rewrite -f nine.conf abcdefghijklmnop
abcdefghijklmnop -> ihgfedcba [0:ok]
libraries/librewrite$ cat eleven.conf
rewriteEngine on
rewriteContext default
rewriteRule "(.)(.)(.)(.)(.)(.)(.)(.)(.)(.)(.)" "$11$10$9$8$7$6$5$4$3$2$1" :
libraries/librewrite$ ./rewrite -f eleven.conf abcdefghijklmnop
abcdefghijklmnop -> a1a0ihgfedcba [0:ok]
I guess no one has needed that many yet... :)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9185
Bug ID: 9185
Summary: glue entry
Product: OpenLDAP
Version: 2.4.48
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: gnoe(a)symas.com
Target Milestone: ---
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
https://bugs.openldap.org/show_bug.cgi?id=9323
Issue ID: 9323
Summary: For 2.5, only support OpenSSL 1.0 or later
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Need to abort configure at the least if the OpenSSL release is less than the
1.0.x series when compiling against OpenSSL
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9302
Issue ID: 9302
Summary: ppolicy pwdFailureTime race condition leaves acccount
unlocked, violating pwdLockout policy
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: requate(a)univention.de
Target Milestone: ---
Multiple concurrent ldap binds with invalid passwords against a user account
sometimes don't trigger account lockout, even though the number of failed
attempts exceeds the configured pwdLockout policy of the ppolicy overlay.
How to reproduce:
1. Configure ppolicy overlay with pwdLockout: TRUE
2. set pwdMaxFailure to some value, e.g. 5
3. Create a test user account and start just enough (or more) parallel
ldapsearch processes
to make the account get locked, e.g. like this in bash/sh (note the
backgrounding):
for i in $(seq 6); do
ldapsearch -x -D "uid=testuser1,$ldap_base" -w invalid >/dev/null 2>&1 &
done
4. Check relevant ppolicy attributes, like:
ldapsearch -x -H LDAPI:// -b "uid=testuser1,$ldap_base" + \
grep -E '^(pwdFailureTime|pwdAccountLockedTime):'
This often shows no pwdAccountLockedTime but enough (or more) pwdFailureTime
values to meet the lockout policy.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9320
Issue ID: 9320
Summary: ldapsearch nettimeout doesn't work with startTls when
the server address is not reachable
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: allen.zhang(a)audiocodes.com
Target Milestone: ---
We found that ldapsearch doesn't return with failure according to the
nettimeout when the server address is not valid. it fails only after TCP
timeout (about 120 seconds in my environment).
we dug into in to the source code and found that :
in common.c, we set the nettimeout after ldap_start_tls_s is called.
We tried to call "ldap_set_option( ld, LDAP_OPT_NETWORK_TIMEOUT, (void *)
&nettimeout )" before ldap_start_tls_s and it works well!
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8159
--- Comment #1 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
So if the argument is "hard", then the code will use the "hard" limit set to
the general "sizelimit" parameter.
--
You are receiving this mail because:
You are on the CC list for the issue.