- openldap-bugs - openldap.org

Re: (ITS#8543) CVE-2015-3276: incorrect multi-keyword mode cipherstring parsing
by he＠NetBSD.org 14 Dec '16

14 Dec '16

>> CVE-2015-3276 appears to be unfixed in 2.4.44, and from several >> attempts at finding the bug reported in your mailing list archive >> I came up empty. So ... The best I've found from this CVE is >> RedHat's bugzilla entry at >> >> https://bugzilla.redhat.com/show_bug.cgi?id=3D1238322 >> >> which contains a (suggested) patch. > > We can integrate a suggested fix if the patch author submits their > patch to our ITS directly. Due to IPR concerns we don't accept or act= > on 3rd party patch submissions. Hm, ok. I've submitted an update to the above bug entry petitioning for them to release the fix. We'll see if they act on it. Regards, - H=E5vard

1 0

(ITS#8545) Undesired timeout when polling for results
by shalopo＠gmail.com 14 Dec '16

14 Dec '16

Full_Name: Shahar Lupu Version: 2.4.44 OS: Ubuntu URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.218.29.26) When calling ldap_result with a timeout={0,0} (polling), it returns LDAP_TIMEOUT even though there are available messages in the socket. This occurs when calling ldap_results with all=true and a multi-message response has arrived. In this case, if the client has already received on the socket every message for the response, it is desirable that all the messages are collected within this ldap_result call. Instead of only polling for the specified timeout, ldap_result applies the timeout (zero when polling) on the wait4msg loop. Consequently, ldap_result returns LDAP_TIMEOUT after the first message if the response is composed of more than one message. While it may be a good idea to apply a timeout for the wai4msg loop (rather than only the polling on the socket), it is undesirable in some cases and should at least be configurable. Or perhaps timeout=polling should never be applied on the wait4msg loop.

1 0

Re: (ITS#8543) CVE-2015-3276: incorrect multi-keyword mode cipherstring parsing
by quanah＠symas.com 13 Dec '16

13 Dec '16

--On Tuesday, December 13, 2016 10:44 AM +0000 hyc(a)symas.com wrote: > he(a)NetBSD.org wrote: >> Full_Name: Havard Eidnes >> Version: 2.4.44 >> OS: NetBSD >> URL: >> Submission from: (NULL) (2001:700:1:0:eeb1:d7ff:fe59:fbaa) >> >> >> Hi, >> >> CVE-2015-3276 appears to be unfixed in 2.4.44, and from several >> attempts at finding the bug reported in your mailing list archive >> I came up empty. So ... The best I've found from this CVE is >> RedHat's bugzilla entry at >> >> https://bugzilla.redhat.com/show_bug.cgi?id=3D1238322 >> >> which contains a (suggested) patch. > > We can integrate a suggested fix if the patch author submits their patch = > to=20 > our ITS directly. Due to IPR concerns we don't accept or act on 3rd party= > =20 > patch submissions. I would also note that MozNSS is not an officially supported TLS library for OpenLDAP, and the hack that was added for 2.4 will be removed in the future (likely OpenLDAP 2.5 and later). End administrators should generally avoid MozNSS entirely. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8544) manpage fixes
by sca+openldap＠andreasschulze.de 13 Dec '16

13 Dec '16

Full_Name: Andreas Schulze Version: git OS: linux URL: ftp://ftp.openldap.org/incoming/andreas-schulze-161213.patch Submission from: (NULL) (2001:a60:f0b4:e502::152) I uploaded a patch to polish some manpages. All changes are suggested by debian lintian - phrase "allows one to" instead of "allows to" - some occurences of -foo have to be written as \-foo in a manpage Andreas

1 0

Re: (ITS#8543) CVE-2015-3276: incorrect multi-keyword mode cipherstring parsing
by hyc＠symas.com 13 Dec '16

13 Dec '16

he(a)NetBSD.org wrote: > Full_Name: Havard Eidnes > Version: 2.4.44 > OS: NetBSD > URL: > Submission from: (NULL) (2001:700:1:0:eeb1:d7ff:fe59:fbaa) > > > Hi, > > CVE-2015-3276 appears to be unfixed in 2.4.44, and from several > attempts at finding the bug reported in your mailing list archive > I came up empty. So ... The best I've found from this CVE is > RedHat's bugzilla entry at > > https://bugzilla.redhat.com/show_bug.cgi?id=3D1238322 > > which contains a (suggested) patch. We can integrate a suggested fix if the patch author submits their patch = to=20 our ITS directly. Due to IPR concerns we don't accept or act on 3rd party= =20 patch submissions. > > Summarized: > > The openldap (for NSS) emulation of the openssl cipherstring parsing= code > incorrectly implements the multi-keyword mode. > As a consequence anyone using a combination like: > > ECDH+SHA > > will not get the expected set of ciphers [...] > > (I'm somewhat dismayed that this was apparently not reported upstream > earlier...) > > Best regards, > > - H=C3=A5vard > > > --=20 -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#8543) CVE-2015-3276: incorrect multi-keyword mode cipherstring parsing
by he＠NetBSD.org 13 Dec '16

13 Dec '16

Full_Name: Havard Eidnes Version: 2.4.44 OS: NetBSD URL: Submission from: (NULL) (2001:700:1:0:eeb1:d7ff:fe59:fbaa) Hi, CVE-2015-3276 appears to be unfixed in 2.4.44, and from several attempts at finding the bug reported in your mailing list archive I came up empty. So ... The best I've found from this CVE is RedHat's bugzilla entry at https://bugzilla.redhat.com/show_bug.cgi?id=1238322 which contains a (suggested) patch. Summarized: The openldap (for NSS) emulation of the openssl cipherstring parsing code incorrectly implements the multi-keyword mode. As a consequence anyone using a combination like: ECDH+SHA will not get the expected set of ciphers [...] (I'm somewhat dismayed that this was apparently not reported upstream earlier...) Best regards, - Håvard

1 0

(ITS#8542) mdb_dbi_open() can break mainDB cursors
by h.b.furuseth＠usit.uio.no 10 Dec '16

10 Dec '16

Full_Name: Hallvard B Furuseth Version: LMDB_0.9.18 OS: URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-161210.c Submission from: (NULL) (81.191.45.31) Submitted by: hallvard ...because mdb_dbi_open() does not track its cursor. Demo enclosed. Fix: Put the mdb_cursor_put() in WITH_CURSOR_TRACKING(mc, ...). I do wonder why failing to track one cursor apparently breaks another cursor, instead of the un-tracked one. Though maybe the un-tracked cursor is broken, and writing through it goes to the wrong place.

1 0

Re: (ITS#8541) test062 periodically core dumps
by quanah＠symas.com 08 Dec '16

08 Dec '16

--On Thursday, December 08, 2016 11:57 PM +0000 quanah(a)openldap.org wrote: > Full_Name: Quanah Gibson-Mount > Version: HEAD > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (47.208.148.26) > > > When running test062, it sometimes core dumps in syncprov abandon. I will > directly email the backtrace as the ITS software breaks them horribly. build@c7build:~$ gdb ~/git/symas-packages/thirdparty/openldap/build/RHEL7_64/symas-openldap/rpm/BUILD/openldap-2.4.45/servers/slapd/.libs/lt-slapd /tmp/core-lt-slapd-11-503-503-4174-1481240987 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/build/git/symas-packages/thirdparty/openldap/build/RHEL7_64/symas-openldap/rpm/BUILD/openldap-2.4.45/servers/slapd/.libs/lt-slapd...done. [New LWP 4264] [New LWP 4189] [New LWP 4174] [New LWP 4204] [New LWP 4265] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/home/build/git/symas-packages/thirdparty/openldap/build/RHEL7_64/symas-openlda'. Program terminated with signal 11, Segmentation fault. #0 0x00007f799db90b7b in syncprov_op_abandon (op=0x7f799db898c0, rs=0x7f799db89700) at syncprov.c:1154 1154 if ( so->s_op->o_connid == op->o_connid && (gdb) thr apply all bt full Thread 5 (Thread 0x7f799d389700 (LWP 4265)): #0 0x00007f79a35dacb1 in clone () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f79a47f9d00 in ?? () from /lib64/libpthread.so.0 No symbol table info available. #2 0x00007f799d389700 in ?? () No symbol table info available. #3 0x0000000000000000 in ?? () No symbol table info available. Thread 4 (Thread 0x7f799e59b700 (LWP 4204)): #0 0x00007f79a47fff4d in __lll_lock_wait () from /lib64/libpthread.so.0 No symbol table info available. #1 0x00007f79a47fbd02 in _L_lock_791 () from /lib64/libpthread.so.0 No symbol table info available. #2 0x00007f79a47fbc08 in pthread_mutex_lock () from /lib64/libpthread.so.0 No symbol table info available. #3 0x00007f79a51e5873 in ldap_pvt_thread_mutex_lock (mutex=0x20ecbb0) at thr_posix.c:300 No locals. #4 0x000000000043dbd8 in connection_operation (ctx=0x7f799e59abb0, arg_v=0x7f7990002670) at connection.c:1150 rc = 0 cancel = 32633 op = 0x7f7990002670 rs = {sr_type = REP_RESULT, sr_tag = 107, sr_msgid = 2, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = {sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 0, r_v2ref = 0x0}, sru_sasl = {r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} tag = 74 opidx = SLAP_OP_DELETE conn = 0x20ecb98 memctx = 0x7f7990002ba0 memctx_null = 0x0 memsiz = 1048576 __PRETTY_FUNCTION__ = "connection_operation" #5 0x000000000043e0d0 in connection_read_thread (ctx=0x7f799e59abb0, argv=0x9) at connection.c:1283 rc = 0 cri = {op = 0x7f7990002670, func = 0x0, arg = 0x0, ctx = 0x7f799e59abb0, nullop = 0} s = 9 #6 0x00007f79a51e416a in ldap_int_thread_pool_wrapper (xpool=0x2083dc0) at tpool.c:956 pq = 0x2083dc0 pool = 0x2083cb0 task = 0x7f79980008c0 work_list = 0x2083e30 ctx = {ltu_pq = 0x2083dc0, ltu_id = 140160324450048, ltu_key = {{ltk_key = 0x43d647 <conn_counter_init>, ltk_data = 0x7f7990002a90, ltk_free = 0x43d499 <conn_counter_destroy>}, { ltk_key = 0x4b206b <slap_sl_mem_init>, ltk_data = 0x7f7990002ba0, ltk_free = 0x4b1e90 <slap_sl_mem_destroy>}, {ltk_key = 0x4587e9 <slap_op_free>, ltk_data = 0x0, ltk_free = 0x45873c <slap_op_q_destroy>}, {ltk_key = 0x0, ltk_data = 0x7f79901088a0, ltk_free = 0x0}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0x0} <repeats 28 times>}} kctx = 0x0 i = 32 keyslot = 486 hash = 3071177190 pool_lock = 0 freeme = 0 __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #7 0x00007f79a47f9dc5 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #8 0x00007f79a35daced in clone () from /lib64/libc.so.6 No symbol table info available. Thread 3 (Thread 0x7f79a564c740 (LWP 4174)): #0 0x00007f79a47faef7 in pthread_join () from /lib64/libpthread.so.0 No symbol table info available. #1 0x00007f79a51e5761 in ldap_pvt_thread_join (thread=140160332842752, thread_return=0x0) at thr_posix.c:201 No locals. #2 0x000000000043aa65 in slapd_daemon () at daemon.c:2910 i = 0 rc = 0 #3 0x0000000000415be4 in main (argc=8, argv=0x7fff32256928) at main.c:1018 i = -1 no_detach = 1 rc = -12 urls = 0x204e0b0 "ldap://localhost:9011/" username = 0x0 groupname = 0x0 sandbox = 0x0 syslogUser = 160 pid = 32633 waitfds = {841312160, 32767} g_argc = 8 g_argv = 0x7fff32256928 configfile = 0x0 configdir = 0x204e090 "./slapd.d" serverName = 0x7fff322584cb "lt-slapd" serverMode = 1 scp = 0x0 scp_entry = 0x0 debug_unknowns = 0x0 syslog_unknowns = 0x0 serverNamePrefix = 0x4fd618 "" l = 140734034700584 slapd_pid_file_unlink = 0 slapd_args_file_unlink = 0 firstopt = 0 __PRETTY_FUNCTION__ = "main" Thread 2 (Thread 0x7f799ed9c700 (LWP 4189)): #0 0x00007f79a35db2c3 in epoll_wait () from /lib64/libc.so.6 No symbol table info available. #1 0x00000000004398a6 in slapd_daemon_task (ptr=0x22acd80) at daemon.c:2517 ns = 1 at = 0 nfds = 4 revents = 0x2057db0 tvp = 0x0 cat = {tv_sec = 0, tv_usec = 0} i = 1 nwriters = 0 now = 1481240987 tv = {tv_sec = 0, tv_usec = 0} tdelta = 1 rtask = 0x0 l = 1 last_idle_check = 1481240984 ebadf = 0 tid = 0 #2 0x00007f79a47f9dc5 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #3 0x00007f79a35daced in clone () from /lib64/libc.so.6 No symbol table info available. Thread 1 (Thread 0x7f799db8a700 (LWP 4264)): #0 0x00007f799db90b7b in syncprov_op_abandon (op=0x7f799db898c0, rs=0x7f799db89700) at syncprov.c:1154 on = 0x7f7990112790 si = 0x7f7990111dd0 so = 0x20 sop = 0x7f7990002270 #1 0x000000000046765b in fe_op_abandon (op=0x7f799db898c0, rs=0x7f799db89700) at abandon.c:136 No locals. #2 0x000000000043cb11 in connection_abandon (c=0x20ecb98) at connection.c:732 rs = {sr_type = REP_RESULT, sr_tag = 0, sr_msgid = 0, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = {sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 0, r_v2ref = 0x0}, sru_sasl = {r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} o = 0x7f7990002670 next = 0x7f7994100930 op = {o_hdr = 0x7f799db89770, o_tag = 80, o_time = 0, o_tincr = 0, o_bd = 0x20a7870, o_req_dn = {bv_len = 0, bv_val = 0x0}, o_req_ndn = {bv_len = 0, bv_val = 0x0}, o_request = { oq_add = {rs_modlist = 0x2, rs_e = 0x0}, oq_bind = {rb_method = 2, rb_cred = {bv_len = 0, bv_val = 0x0}, rb_edn = {bv_len = 0, bv_val = 0x0}, rb_ssf = 0, rb_mech = { bv_len = 0, bv_val = 0x0}}, oq_compare = {rs_ava = 0x2}, oq_modify = {rs_mods = {rs_modlist = 0x2, rs_no_opattrs = 0 '\000'}, rs_increment = 0}, oq_modrdn = {rs_mods = { rs_modlist = 0x2, rs_no_opattrs = 0 '\000'}, rs_deleteoldrdn = 0, rs_newrdn = {bv_len = 0, bv_val = 0x0}, rs_nnewrdn = {bv_len = 0, bv_val = 0x0}, rs_newSup = 0x0, rs_nnewSup = 0x0}, oq_search = {rs_scope = 2, rs_deref = 0, rs_slimit = 0, rs_tlimit = 0, rs_limit = 0x0, rs_attrsonly = 0, rs_attrs = 0x0, rs_filter = 0x0, rs_filterstr = { bv_len = 0, bv_val = 0x0}}, oq_abandon = {rs_msgid = 2}, oq_cancel = {rs_msgid = 2}, oq_extended = {rs_reqoid = {bv_len = 2, bv_val = 0x0}, rs_flags = 0, rs_reqdata = 0x0}, oq_pwdexop = {rs_extended = {rs_reqoid = {bv_len = 2, bv_val = 0x0}, rs_flags = 0, rs_reqdata = 0x0}, rs_old = {bv_len = 0, bv_val = 0x0}, rs_new = { bv_len = 0, bv_val = 0x0}, rs_mods = 0x0, rs_modtail = 0x0}}, o_abandon = 0, o_cancel = 0, o_groups = 0x0, o_do_not_cache = 0 '\000', o_is_auth_check = 0 '\000', o_dont_replicate = 0 '\000', o_acl_priv = ACL_NONE, o_nocaching = 0 '\000', o_delete_glue_parent = 0 '\000', o_no_schema_check = 0 '\000', o_no_subordinate_glue = 0 '\000', o_ctrlflag = '\000' <repeats 31 times>, o_controls = 0x0, o_authz = {sai_method = 0, sai_mech = {bv_len = 0, bv_val = 0x0}, sai_dn = {bv_len = 0, bv_val = 0x0}, sai_ndn = { bv_len = 0, bv_val = 0x0}, sai_ssf = 0, sai_transport_ssf = 0, sai_tls_ssf = 0, sai_sasl_ssf = 0}, o_ber = 0x0, o_res_ber = 0x0, o_callback = 0x0, o_ctrls = 0x0, o_csn = { bv_len = 0, bv_val = 0x0}, o_private = 0x0, o_extra = {slh_first = 0x0}, o_next = {stqe_next = 0x0}} ohdr = {oh_opid = 0, oh_connid = 1004, oh_conn = 0x20ecb98, oh_msgid = 0, oh_protocol = 0, oh_tid = 0, oh_threadctx = 0x0, oh_tmpmemctx = 0x0, oh_tmpmfuncs = 0x0, oh_counters = 0x0, oh_log_prefix = '\000' <repeats 255 times>} #3 0x000000000043cebd in connection_closing (c=0x20ecb98, why=0x505940 <conn_lost_str> "connection lost") at connection.c:802 __PRETTY_FUNCTION__ = "connection_closing" #4 0x000000000043ea0f in connection_read (s=9, cri=0x7f799db89b60) at connection.c:1472 rc = -2 c = 0x20ecb98 __PRETTY_FUNCTION__ = "connection_read" #5 0x000000000043e031 in connection_read_thread (ctx=0x7f799db89bb0, argv=0x9) at connection.c:1276 rc = 0 cri = {op = 0x7f7994100930, func = 0x0, arg = 0x0, ctx = 0x7f799db89bb0, nullop = 0} s = 9 #6 0x00007f79a51e416a in ldap_int_thread_pool_wrapper (xpool=0x2083dc0) at tpool.c:956 pq = 0x2083dc0 pool = 0x2083cb0 task = 0x7f7998000b40 work_list = 0x2083e30 ctx = {ltu_pq = 0x2083dc0, ltu_id = 140160313894656, ltu_key = {{ltk_key = 0x4b206b <slap_sl_mem_init>, ltk_data = 0x7f79940008c0, ltk_free = 0x4b1e90 <slap_sl_mem_destroy>}, { ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0x0} <repeats 31 times>}} kctx = 0x0 i = 32 keyslot = 84 hash = 4081317972 pool_lock = 0 freeme = 0 __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #7 0x00007f79a47f9dc5 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #8 0x00007f79a35daced in clone () from /lib64/libc.so.6 No symbol table info available. -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8541) test062 periodically core dumps
by quanah＠openldap.org 08 Dec '16

08 Dec '16

Full_Name: Quanah Gibson-Mount Version: HEAD OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) When running test062, it sometimes core dumps in syncprov abandon. I will directly email the backtrace as the ITS software breaks them horribly.

1 0

(ITS#8540) Expand test suite to include TLS tests
by quanah＠openldap.org 08 Dec '16

08 Dec '16

Full_Name: Quanah Gibson-Mount Version: 2.4.44 OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) The test suite should be expanded to have SSL related test. To do this, we'll need a CA cert, server cert for "localhost", and a couple of user certs (for babs and/or bjorn). Test can then validate startTLS, ldaps, and client cert auth, using both an exact matching DN for one user and one requiring an authz-regexp map. Tests only run if SSL was enabled for the build.

1 0

Re: (ITS#8504) LDMB: Return EPIPE from mdb_env_copyfd2 instead abort on SIGPIPE
by lmb＠cloudflare.com 07 Dec '16

07 Dec '16

Is there anything required from me to make this patch move along?

1 0

Re: (ITS#8533) Support OpenSSL-1.1.0c
by sca＠andreasschulze.de 04 Dec '16

04 Dec '16

Am 28.11.2016 um 17:42 schrieb Quanah Gibson-Mount: > I have a few additional comments: > ... I updated the patch as suggested: ftp://ftp.openldap.org/incoming/andreas-schulze-161204.patch Andreas

1 0

(ITS#8539) Fix regression suite to do all backends
by quanah＠openldap.org 02 Dec '16

02 Dec '16

Full_Name: Quanah Gibson-Mount Version: 2.4.44 OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) When running the regression suite via "make its" it will only run with the first defined backend, rather than all compiled backends like the test suite does. This needs to be fixed.

1 0

(ITS#8538) Update slapd.conf/slapd-config (5) to note interval is requird for syncrepl config
by quanah＠openldap.org 02 Dec '16

02 Dec '16

Full_Name: Quanah Gibson-Mount Version: 2.4.44 OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) The slapd.conf/slapd-config (5) man pages need to be updated to note that the "interval" parameter to olcSyncrepl is required.

1 0

Re: (ITS#8521) Cannot have replication working after setting up the replication config in slapd.d
by elecharny＠gmail.com 02 Dec '16

02 Dec '16

Actually, it's an invalid issue. The problem is all in teh sequence of updates on the provider. There are 6 possible scenario, depending on which order we inject the serverID, teh syncprov overlay and the data : 1) data, serverID, syncprov : invalid. All the data will have a wrong entryCSN 2) data, syncprov,serverID : invalid, same reason 3) serverID, syncprov, data : All work properly 4) syncprov, serverID, data : All work properly 5) serverID, data, syncprov : the corner case scenario... Syncprov has no way to know which contextCSN to generate. The only way for the server to replicate is to do an update, so that the contextCSN is properly generated. 6) syncprov, data, serverID : invalid. All the data will have a wrong entryCSN Bottom line, *always* inject the serverID and syncprov *before injecting some data, or be ready to do an update after having injected syncprov and serverID. =20 Le 21/10/16 =C3=A0 23:45, openldap-its(a)OpenLDAP.org a =C3=A9crit : > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** > > Thanks for your report to the OpenLDAP Issue Tracking System. Your > report has been assigned the tracking number ITS#8521. > > One of our support engineers will look at your report in due course. > Note that this may take some time because our support engineers > are volunteers. They only work on OpenLDAP when they have spare > time. > > If you need to provide additional information in regards to your > issue report, you may do so by replying to this message. Note that > any mail sent to openldap-its(a)openldap.org with (ITS#8521) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=3D(ITS#8521) > > You may follow the progress of this report by loading the following > URL in a web browser: > http://www.OpenLDAP.org/its/index.cgi?findid=3D8521 > > Please remember to retain your issue tracking number (ITS#8521) > on any further messages you send to us regarding this report. If > you don't then you'll just waste our time and yours because we > won't be able to properly track the report. > > Please note that the Issue Tracking System is not intended to > be used to seek help in the proper use of OpenLDAP Software. > Such requests will be closed. > > OpenLDAP Software is user supported. > http://www.OpenLDAP.org/support/ > > -------------- > Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. > --=20 Emmanuel Lecharny Symas.com directory.apache.org

1 0

Re: (ITS#8521) Cannot have replication working after setting up the replication config in slapd.d
by elecharny＠gmail.com 02 Dec '16

02 Dec '16

FTR, the check on slapd_serverID presence has been added in ITS#8281. Le 21/10/16 =C3=A0 23:45, openldap-its(a)OpenLDAP.org a =C3=A9crit : > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** > > Thanks for your report to the OpenLDAP Issue Tracking System. Your > report has been assigned the tracking number ITS#8521. > > One of our support engineers will look at your report in due course. > Note that this may take some time because our support engineers > are volunteers. They only work on OpenLDAP when they have spare > time. > > If you need to provide additional information in regards to your > issue report, you may do so by replying to this message. Note that > any mail sent to openldap-its(a)openldap.org with (ITS#8521) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=3D(ITS#8521) > > You may follow the progress of this report by loading the following > URL in a web browser: > http://www.OpenLDAP.org/its/index.cgi?findid=3D8521 > > Please remember to retain your issue tracking number (ITS#8521) > on any further messages you send to us regarding this report. If > you don't then you'll just waste our time and yours because we > won't be able to properly track the report. > > Please note that the Issue Tracking System is not intended to > be used to seek help in the proper use of OpenLDAP Software. > Such requests will be closed. > > OpenLDAP Software is user supported. > http://www.OpenLDAP.org/support/ > > -------------- > Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. > --=20 Emmanuel Lecharny Symas.com directory.apache.org

1 0

Re: (ITS#8521) Cannot have replication working after setting up the replication config in slapd.d
by elecharny＠gmail.com 02 Dec '16

02 Dec '16

The problem is that if we already have a ServerID on the producer, it will never generate a contextCSN, waiting for the consumer to send one, or for an update to occur : static int syncprov_db_open( BackendDB *be, ConfigReply *cr ) { ... /* Didn't find a contextCSN, should we generate one? */ if ( !si->si_ctxcsn ) { char csnbuf[ LDAP_PVT_CSNSTR_BUFSIZE ]; struct berval csn; if ( slap_serverID || SLAP_SYNC_SHADOW( op->o_bd )) { /* If we're also a consumer, then don't generate anything. * Wait for our provider to send it to us, or for a local * modify if we have multimaster. */ goto out; } At this point, nothing happens when teh consumer connects for teh very first time, because it is expected to send a contextCSN, which it obviously don't have. I do think that the provider should always generate a contextCSN for its own data, when the syncprov overlay is added. that should solve the problem. Now, I don't know (yet) what would be the impact on replication if we do so. Still investigating... -- Emmanuel Lecharny Symas.com directory.apache.org

1 0

Re: (ITS#8536) Solaris unable to login to open ldap
by quanah＠symas.com 01 Dec '16

01 Dec '16

--On Thursday, December 01, 2016 3:04 PM +0000 sameer.shaikh(a)wipro.com wrote: > Full_Name: sameer > Version: 2.4.40 > OS: solaris 10 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (195.80.64.88) Hello, The ITS system is for reporting bugs. This does not appear to be a bug report. If you require help with configuring your LDAP server and you are using OpenLDAP, then you should subscribe to the openldap-technical(a)openldap.org mailing list and post your questions there. This ITS will be closed. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8537) liblmdb errors with data=NULL and non-matching SET_KEY
by h.b.furuseth＠usit.uio.no 01 Dec '16

01 Dec '16

Related issue: mdb_cursor_prev/mdb_cursor_last() with data==NULL position the xcursor at 1st data item, while data!=NULL puts it at last item. That's unintuitive and should either be documented or normalized - but changing it can break existing programs. In the cases when it didn't just fail earlier, anyway: mdb_cursor_prev(), and maybe mdb_cursor_last() on a sub-DB. Haven't tested the latter. Whatever mdb_cursor_last() ends up doing, I think mdb_cursor_prev() should do the same. There is positioning code inside if(data) elsewhere too, but defaults to doing cursor_first() or something similar. Don't know if that can have any visible effect on the next operation. -- Hallvard

1 0

(ITS#8537) liblmdb errors with data=NULL and non-matching SET_KEY
by h.b.furuseth＠usit.uio.no 01 Dec '16

01 Dec '16

Full_Name: Hallvard B Furuseth Version: mdb.master, fa83b25ec536ac2642f8e0d3c6bf587008513ef4 OS: Linux x86_64 URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-161201.c Submission from: (NULL) (129.240.203.186) Submitted by: hallvard liblmdb can crash or give an EINVAL in some cases after it forgets to initialize an xcursor on a sub-page: To fail the init, use next/prev with data=NULL, or SET_KEY to a non-existe k key (so it gets positioned on next key). Then try to use the cursor in another operation. Test program enclosed.

1 0

(ITS#8536) Solaris unable to login to open ldap
by sameer.shaikh＠wipro.com 01 Dec '16

01 Dec '16

Full_Name: sameer Version: 2.4.40 OS: solaris 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.80.64.88) i have update below schema # ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/cosine.ldif # ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/nis.ldif # ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/inetorgperson.ldif # ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/openldap/schema/ppolicy.ldif Followinthe docuemnt but below is the error still recieved Dec 1 14:58:32 hnmpvdbs01 sshd[3078]: [ID 685508 auth.info] libgss dlopen(/usr/lib/gss/mech_spnego.so.1): ld.so.1: sshd: fatal: /usr/lib/gss/mech_spnego.so.1: open failed: No such file or directory Dec 1 14:58:35 hnmpvdbs01 sshd[3078]: [ID 800047 auth.info] Illegal user sameer from 10.200.10.30 Dec 1 14:58:35 hnmpvdbs01 sshd[3078]: [ID 800047 auth.info] input_userauth_request: illegal user sameer Dec 1 14:58:35 hnmpvdbs01 sshd[3078]: [ID 800047 auth.info] Failed none for <invalid username> from 10.200.10.30 port 49362 ssh2 Dec 1 14:58:38 hnmpvdbs01 sshd[3078]: [ID 219349 auth.debug] pam_unix_auth: user sameer not found Dec 1 14:58:38 hnmpvdbs01 sshd[3078]: [ID 800047 auth.info] Keyboard-interactive (PAM) userauth failed[13] while authenticating: No account present for user Dec 1 14:58:38 hnmpvdbs01 sshd[3078]: [ID 800047 auth.info] Failed keyboard-interactive for <invalid username> from 10.200.10.30 port 49362 ssh2

1 0

(ITS#8535) ITS4337 regression test failure
by quanah＠openldap.org 30 Nov '16

30 Nov '16

Full_Name: Quanah Gibson-Mount Version: 2.4.44 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) The regression test for ITS4337 currently fails due to a bad script and bad configuration file. Fix incoming.

1 0

(ITS#8534) ITS4336 regression test failure
by quanah＠openldap.org 30 Nov '16

30 Nov '16

Full_Name: Quanah Gibson-Mount Version: 2.4.44 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.26) The regression test for ITS4336 fails due to an incorrect configuration file. Fix incoming.

1 0

Re: (ITS#8521) Cannot have replication working after setting up the replication config in slapd.d
by quanah＠symas.com 29 Nov '16

29 Nov '16

--On Friday, October 21, 2016 11:02 PM +0000 elecharny(a)gmail.com wrote: > o Step 3 : On the consumer, we inject the following entry : > ># Context entry > dn: dc=3Dexample,dc=3Dcom > changetype: add > objectClass: domain > objectClass: top > dc: example This step is not valid. The consumer should have no pre-existing data that differs from the provider's database. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8533) Support OpenSSL-1.1.0c
by quanah＠symas.com 28 Nov '16

28 Nov '16

--On Saturday, November 26, 2016 10:50 PM +0000 sca(a)andreasschulze.de wrote: > But I personally need pkg-config because my openssl library is named > libssl-dv / libcrypto-dv > to coexist with the distribution versions. Viktor Dukhovni told me to > build openssl-1.1 that way > and beside the requirement for pkg-config I'm personally fine with > that advise :-) > > should I prepare the new patch to fit your needs? > otherwise I would be fine if you modify the contribution to your needs. > > Anyway: after I wrote the patch for git-master it was very easy to > create a patch to compile also 2.4.44 with openssl-1.1 > I could publish that also next week. Do you think that makes sense? Hi Andreas, Thanks for looking into this. I have a few additional comments: a) "configure.in" should be patched rather than "configure", and then I'd verify that regenerating configure works appropriately. b) A coding style issue found throughout the patch, where you are using NULL == variable rather than variable == NULL. This should be fixed. For example, you have: if ( NULL == tlso_bio_method ) { this instead should be: if ( tlso_bio_method == NULL ) { Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs