- openldap-bugs - openldap.org

Re: (ITS#8844) LMDB mdb_env_close is unsafe in forked child
by h.b.furuseth＠usit.uio.no 14 Jun '18

14 Jun '18

On 14/06/2018 20:34, Howard Chu wrote: > Hallvard Breien Furuseth wrote: >> Wait, what? The child didn't write any pids to the table. If >> there are pids for it to clear, something is wrong. That can be: > > No, there most likely aren't PIDs for it to clear. But most importantly, > it must not clear using env->me_pid since that is still the parent's PID. > >> - The pid is from an older run, and the system reused the pid. If we >> code for this, it should be to clear such pids during mdb_env_open. >> It gets very arbitrary to clear them when the user does env_close() >> in the child and the child happens to have the that reused pid. > > No. If the system reused the PID then that means the previous owner of > that PID is dead already anyway. Right... > If there are any table entries under > that PID there's no problem removing them. The problem is that it's arbitrary. Something is exiting without clearing its pid slots, and 0.001% of the time this code will catch it. Better to skip this cleanup, or to always do it - but "always" belongs in env_open(). If a new env is seeing its pid in use, then it can safely clean it out. Last we talked about that, I liked it and you did not:-) >> - The child opened a new MDB_env with the same path, and closes the >> parent's env afterwards. Don't Do That, users. But what to do in >> this situation, if we are to have code for it, is to do nothing with >> the lockfile. Not close it either, since closing it will lose the >> lock for the env which was opened in the child. > > That's a completely different case. This ITS is specifically about a > process with an open environment that subsequently forks. No, I mean: Parent, pid P: open env A. Child, pid Q: - open and start using env B with the same path. - close env A, while B is still open. With the new code, this clears pid Q - i.e. B's pids. But lmdb.h already lists that as a "don't do that", because it also removes B's lock on the lockfile.

1 0

Re: (ITS#8844) LMDB mdb_env_close is unsafe in forked child
by hyc＠symas.com 14 Jun '18

14 Jun '18

Hallvard Breien Furuseth wrote: > On 02/05/2018 18:05, hyc(a)openldap.org wrote: >> Following on from ITS#8505. >> mdb_env_close0() uses env->me_pid when clearing the readers table. If the env >> was open in a process that forked, and the child process calls mdb_env_close(), >> it will be clearing the wrong PID. Change this to use getpid() instead. > > Wait, what? The child didn't write any pids to the table. If > there are pids for it to clear, something is wrong. That can be: No, there most likely aren't PIDs for it to clear. But most importantly, it must not clear using env->me_pid since that is still the parent's PID. > - The pid is from an older run, and the system reused the pid. If we > code for this, it should be to clear such pids during mdb_env_open. > It gets very arbitrary to clear them when the user does env_close() > in the child and the child happens to have the that reused pid. No. If the system reused the PID then that means the previous owner of that PID is dead already anyway. If there are any table entries under that PID there's no problem removing them. > - The child opened a new MDB_env with the same path, and closes the > parent's env afterwards. Don't Do That, users. But what to do in > this situation, if we are to have code for it, is to do nothing with > the lockfile. Not close it either, since closing it will lose the > lock for the env which was opened in the child. That's a completely different case. This ITS is specifically about a process with an open environment that subsequently forks. -- -- 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#8865) Publish admin guide in epub format
by dpa-bugs＠aegee.org 11 Jun '18

11 Jun '18

Full_Name: Dilian Palauzov Version: OS: URL: Submission from: (NULL) (87.118.146.153) Please offer the admin guide for downloading also in epub format. The guide is written in sdf, this could be converted to POD and then to EPUB. SDF offers also output in SGML, this can probably be converted to EPUB, too.

1 0

Re: (ITS#8573) ldap* tools should be able to function w/o a conf file
by ondra＠mistotebe.net 11 Jun '18

11 Jun '18

On Mon, Jan 23, 2017 at 11:43:59PM +0000, quanah(a)openldap.org wrote: > 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) > > > Right now, it is impossible to configure the ldap* command line tools so that > they function in major circumstances w/o also having a configuration file (I.e., > ldap.conf, .ldaprc, etc). For example, the ability to use startTLS with LDAP > requires such a file so that the CA file and/or cert path for the tool can be > defined. > > The "-o" option should be expanded to cover additional configuration parameters > from the conf file, as has already been done with the network timeout parameter. I have updated the documentation to extract the new options into ldap.conf(5) and reference it from each tool instead. The commits at https://github.com/mistotebe/openldap/tree/its8573-tables contain that change. -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

(ITS#8864) ber_realloc doesn't update ber_rwptr
by ondra＠openldap.org 08 Jun '18

08 Jun '18

Full_Name: Ondrej Kuznik Version: master/re24 OS: URL: https://github.com/mistotebe/openldap/tree/ITS8864 Submission from: (NULL) (82.10.24.68) Running a ber_flush that doesn't manage to send everything and then adding data to the BerElement that ends up with its buffer reallocated will not update ber_rwptr, causing the following flush to fail. Patch available at the link above.

1 0

Re: (ITS#8731) Variadic Debug() macro
by ondra＠mistotebe.net 06 Jun '18

06 Jun '18

On Tue, Sep 12, 2017 at 12:55:20PM +0000, okuznik(a)symas.com wrote: > The patch series in the linked archive changes the logging macros to be fully > variadic: There is a new archive at: ftp://ftp.openldap.org/incoming/debug_macro_refactor_v2.tgz This addresses concerns that it should still be possible to build libldap (only) on compilers that might not support variadic macros. All patches are generated from the attached .cocci files against current master (commit 9069cbe543d079e9d7f55162decb8e732fc32338). I would welcome some review of the patch 01-logging.patch, which consists of the actual implementation. Rest is just to bring OpenLDAP up to scratch. At the end of the series, OpenLDAP seems to compile with CFLAGS containing -Werror=format-extra-args. -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#8863) openldap compilation failure when
by ramakanth.varala＠gmail.com 06 Jun '18

06 Jun '18

# It's possible (for near-UNIX clones) that sys_errlist doesn't exist if test $ol_cv_dcl_sys_errlist = no ; then above lines are from configure script , i don't want my binaries and libraries do be dependent on the symbols of errlist and nerr . As per mail trace "Re: How to get rid of sys_errlist and sys_nerr? - OpenLDAP" , this issue seems to existing from long back. The solution given is still not working. On 6/6/18, Howard Chu <hyc(a)symas.com> wrote: > ramakanth.varala(a)gmail.com wrote: >> Full_Name: Rama Kanth Varala >> Version: 2.4.46 >> OS: Cent OS Release 5.7 >> URL: ftp://ftp.openldap.org/incoming/openldap-bug.txt >> Submission from: (NULL) (72.163.217.107) >> >> >> I am trying to compile my binaries in a machine with has glibc 2.5 . >> Then i >> take these >> ldap libraries to link with the other process which is getting compiled >> in >> glibc 2.3.4. >> >> I am compiling with option of ol_cv_dcl_sys_errlist=no , so that i can >> disable >> offending symbols (sys_nerr and sys_errlist). configure go smooth but >> compilation fails. >> >> Below is the compilation failure trace. >> >> cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include >> -DLDAP_LIBRARY -c string.c -fPIC -DPIC -o .libs/string.o >> cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include >> -DLDAP_LIBRARY -c string.c -o string.o >/dev/null 2>&1 >> /bin/sh ../../libtool --mode=compile cc -g -O2 -I../../include >> -I../../include -I/usr/local/db48/include -DLDAP_LIBRARY -c >> util-int.c >> cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include >> -DLDAP_LIBRARY -c util-int.c -fPIC -DPIC -o .libs/util-int.o >> In file included from /usr/include/stdio.h:754, >> from /usr/include/resolv.h:64, >> from ../../include/ac/socket.h:58, >> from util-int.c:32: >> /usr/include/bits/sys_errlist.h:27: error: expected identifier or '(' >> before numeric constant >> /usr/include/bits/sys_errlist.h:28: error: expected identifier or '(' >> before 'char' >> /usr/include/bits/sys_errlist.h:28: error: expected ')' before numeric >> constant >> make[2]: *** [util-int.lo] Error 1 >> make[2]: Leaving directory >> `/home/admin/bug/openldap-2.4.46/libraries/libldap' >> make[1]: *** [all-common] Error 1 >> make[1]: Leaving directory `/home/admin/bug/openldap-2.4.46/libraries' >> make: *** [all-common] Error 1 > > What makes you think this is an OpenLDAP issue? The error message clearly > says > sys_errlist.h was included from stdio.h - we have no control over that. >> >> Uploading the comple configure log and compilation traces. >> >> > > > -- > -- 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

Re: (ITS#8863) openldap compilation failure when
by hyc＠symas.com 06 Jun '18

06 Jun '18

ramakanth.varala(a)gmail.com wrote: > Full_Name: Rama Kanth Varala > Version: 2.4.46 > OS: Cent OS Release 5.7 > URL: ftp://ftp.openldap.org/incoming/openldap-bug.txt > Submission from: (NULL) (72.163.217.107) > > > I am trying to compile my binaries in a machine with has glibc 2.5 . Then i > take these > ldap libraries to link with the other process which is getting compiled in > glibc 2.3.4. > > I am compiling with option of ol_cv_dcl_sys_errlist=no , so that i can disable > offending symbols (sys_nerr and sys_errlist). configure go smooth but > compilation fails. > > Below is the compilation failure trace. > > cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include > -DLDAP_LIBRARY -c string.c -fPIC -DPIC -o .libs/string.o > cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include > -DLDAP_LIBRARY -c string.c -o string.o >/dev/null 2>&1 > /bin/sh ../../libtool --mode=compile cc -g -O2 -I../../include > -I../../include -I/usr/local/db48/include -DLDAP_LIBRARY -c > util-int.c > cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include > -DLDAP_LIBRARY -c util-int.c -fPIC -DPIC -o .libs/util-int.o > In file included from /usr/include/stdio.h:754, > from /usr/include/resolv.h:64, > from ../../include/ac/socket.h:58, > from util-int.c:32: > /usr/include/bits/sys_errlist.h:27: error: expected identifier or '(' > before numeric constant > /usr/include/bits/sys_errlist.h:28: error: expected identifier or '(' > before 'char' > /usr/include/bits/sys_errlist.h:28: error: expected ')' before numeric constant > make[2]: *** [util-int.lo] Error 1 > make[2]: Leaving directory `/home/admin/bug/openldap-2.4.46/libraries/libldap' > make[1]: *** [all-common] Error 1 > make[1]: Leaving directory `/home/admin/bug/openldap-2.4.46/libraries' > make: *** [all-common] Error 1 What makes you think this is an OpenLDAP issue? The error message clearly says sys_errlist.h was included from stdio.h - we have no control over that. > > Uploading the comple configure log and compilation traces. > > -- -- 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#8863) openldap compilation failure when
by ramakanth.varala＠gmail.com 06 Jun '18

06 Jun '18

Full_Name: Rama Kanth Varala Version: 2.4.46 OS: Cent OS Release 5.7 URL: ftp://ftp.openldap.org/incoming/openldap-bug.txt Submission from: (NULL) (72.163.217.107) I am trying to compile my binaries in a machine with has glibc 2.5 . Then i take these ldap libraries to link with the other process which is getting compiled in glibc 2.3.4. I am compiling with option of ol_cv_dcl_sys_errlist=no , so that i can disable offending symbols (sys_nerr and sys_errlist). configure go smooth but compilation fails. Below is the compilation failure trace. cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include -DLDAP_LIBRARY -c string.c -fPIC -DPIC -o .libs/string.o cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include -DLDAP_LIBRARY -c string.c -o string.o >/dev/null 2>&1 /bin/sh ../../libtool --mode=compile cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include -DLDAP_LIBRARY -c util-int.c cc -g -O2 -I../../include -I../../include -I/usr/local/db48/include -DLDAP_LIBRARY -c util-int.c -fPIC -DPIC -o .libs/util-int.o In file included from /usr/include/stdio.h:754, from /usr/include/resolv.h:64, from ../../include/ac/socket.h:58, from util-int.c:32: /usr/include/bits/sys_errlist.h:27: error: expected identifier or '(' before numeric constant /usr/include/bits/sys_errlist.h:28: error: expected identifier or '(' before 'char' /usr/include/bits/sys_errlist.h:28: error: expected ')' before numeric constant make[2]: *** [util-int.lo] Error 1 make[2]: Leaving directory `/home/admin/bug/openldap-2.4.46/libraries/libldap' make[1]: *** [all-common] Error 1 make[1]: Leaving directory `/home/admin/bug/openldap-2.4.46/libraries' make: *** [all-common] Error 1 Uploading the comple configure log and compilation traces.

1 0

Re: (ITS#8862) typos manual slapd-mdb
by hyc＠symas.com 02 Jun '18

02 Jun '18

dpa-bugs(a)aegee.org wrote: > Full_Name: Dilyan Palauzov > Version: latest > OS: any > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (85.234.198.115) > > > http://www.openldap.org/software/man.cgi?query=slapd-mdb says: The manual is correct. Closing this ITS. > > index {_attrlist_|default} [pres,eq,approx,sub,_special_] > ... > If only an _attr_ is given, the indices specified for default are > maintained. > > It means probably not _attr_ but _attrlist_. > > maxsize _bytes_: > ... > It is important to set this to as large a value as possible > > I am not a native speaker, but I think there shall be no "a" before "value". > > -- -- 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#8862) typos manual slapd-mdb
by dpa-bugs＠aegee.org 01 Jun '18

01 Jun '18

Full_Name: Dilyan Palauzov Version: latest OS: any URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (85.234.198.115) http://www.openldap.org/software/man.cgi?query=slapd-mdb says: index {_attrlist_|default} [pres,eq,approx,sub,_special_] ... If only an _attr_ is given, the indices specified for default are maintained. It means probably not _attr_ but _attrlist_. maxsize _bytes_: ... It is important to set this to as large a value as possible I am not a native speaker, but I think there shall be no "a" before "value".

1 0

(ITS#8861) slapd-(async)meta(5) tls option missing ldaps
by quanah＠openldap.org 01 Jun '18

01 Jun '18

Full_Name: Quanah Gibson-Mount Version: HEAD OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.239) The slapd-asyncmeta(5) and slapd-meta(5) man pages are missing the fact that they support the "ldaps" option to the "tls" keyword. This section should be updated along the lines of back-ldap which also has this option as a keyword.

1 0

Re: (ITS#8860) searching issue
by ryan＠openldap.org 27 May '18

27 May '18

Hello, The ITS is for reporting bugs in the software. For user support please contact the openldap-technical(a)openldap.org mailing list. This ITS will be closed. On Sun, May 27, 2018 at 02:33:05PM +0000, bahaa.mosaad(a)barqsystems.com wrote: >Full_Name: bahaa mosaad ali >Version: 2.4.39-3.el7 >OS: redhat 7 >URL: https://drive.google.com/drive/my-drive >Submission from: (NULL) (41.69.233.85) > > >i have radius server and get openldap to connect with this (server) according to >bind ruels success binding to ldap but when i search for some users without >password i get all info about those users but if i search by command like this >ldapsearch -x -W -D (user) dc= & password the error is always invalid >credentials even if change the password more than one time > >according to this error when trying to authenticate users from radius it would >be fail > > > >

1 0

(ITS#8860) searching issue
by bahaa.mosaad＠barqsystems.com 27 May '18

27 May '18

Full_Name: bahaa mosaad ali Version: 2.4.39-3.el7 OS: redhat 7 URL: https://drive.google.com/drive/my-drive Submission from: (NULL) (41.69.233.85) i have radius server and get openldap to connect with this (server) according to bind ruels success binding to ldap but when i search for some users without password i get all info about those users but if i search by command like this ldapsearch -x -W -D (user) dc= & password the error is always invalid credentials even if change the password more than one time according to this error when trying to authenticate users from radius it would be fail

1 0

Re: (ITS#8616) olcSpNopresent and olcSpReloadHint can't be modified dynamically
by quanah＠symas.com 24 May '18

24 May '18

--On Thursday, May 24, 2018 6:49 PM +0100 Howard Chu <hyc(a)symas.com> wrote: > quanah(a)symas.com wrote: >> --On Tuesday, March 14, 2017 6:58 PM +0000 elecharny(a)symas.com wrote: >> >> Also fails for olcSpSessionLog (if it wasn't defined when the cn=config >> db was loaded) > > Couldn't reproduce this, works for me. I realized the issue I'd hit was with replicating cn=config when modifying this attribute. Likely the missing matching rules issue that's tracked under another ITS I need to address. --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#8616) olcSpNopresent and olcSpReloadHint can't be modified dynamically
by hyc＠symas.com 24 May '18

24 May '18

elecharny(a)symas.com wrote: > Full_Name: Emmanuel Lecharny > Version: 2.4.44 > OS: CentOS > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (86.246.56.212) > > > Adding either the olcSpNoPresent/olcSpReloadHint into a syncprov overlay is > possible using slapd.d. It the values are set to TRUE, you can remove them. If > you set them to FALSE, trying to remove the value get you an error 80. > > Second thing : set the value to TRUE (works), then change it to FALSE (works). > Now, you are stuck : you can't revert it to TRUE or remove them. > > Third thing : set the value to FALSE (works), then you can't change it to TRUE > or delete the attribute. All of these are the same issue. Fixed in master. > > There is no other way that modifyin the ldif file to get it back on its feet. > > -- -- 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

Re: (ITS#8616) olcSpNopresent and olcSpReloadHint can't be modified dynamically
by hyc＠symas.com 24 May '18

24 May '18

quanah(a)symas.com wrote: > --On Tuesday, March 14, 2017 6:58 PM +0000 elecharny(a)symas.com wrote: > > Also fails for olcSpSessionLog (if it wasn't defined when the cn=config db > was loaded) Couldn't reproduce this, works for me. -- -- 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

Re: (ITS#8859) Support backends without a database
by ondra＠mistotebe.net 22 May '18

22 May '18

On Tue, May 22, 2018 at 09:03:28AM +0000, h.b.furuseth(a)usit.uio.no wrote: > On 21. mai 2018 17:07, ondra(a)openldap.org wrote: >> In order to support the load balancer within the slapd process and integrate >> correctly, we declare it to be a backend as that is the best match - allows us >> to register all the callbacks that a subsystem like this needs. (...) > > Please comment SLAP_BFLAG_STANDALONE, explaining this, even though that goes > against the surrounding coding style:-( Also maybe struct BackendInfo could > use a comment about database backends vs database-less backends. I've put a comment there. As for BackendInfo, there should be no difference as far as I understand. But there is probably quite a bit of context I'm still missing. -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#8859) Support backends without a database
by h.b.furuseth＠usit.uio.no 22 May '18

22 May '18

On 21. mai 2018 17:07, ondra(a)openldap.org wrote: > In order to support the load balancer within the slapd process and integrate > correctly, we declare it to be a backend as that is the best match - allows us > to register all the callbacks that a subsystem like this needs. (...) Please comment SLAP_BFLAG_STANDALONE, explaining this, even though that goes against the surrounding coding style:-( Also maybe struct BackendInfo could use a comment about database backends vs database-less backends. -- Hallvard

1 0

(ITS#8859) Support backends without a database
by ondra＠openldap.org 21 May '18

21 May '18

Full_Name: Ondrej Kuznik Version: master OS: URL: https://github.com/mistotebe/openldap/tree/ITS8859 Submission from: (NULL) (82.10.24.68) In order to support the load balancer within the slapd process and integrate correctly, we declare it to be a backend as that is the best match - allows us to register all the callbacks that a subsystem like this needs. The only problem is that slapd will skip startup for backends that are not used by at least one database. The linked patch deals with this limitation and a few bugs encountered along the way (some code has not been exercised in a long time and has suffered from some bitrot). The support to provide backend global configuration was nominally present but has never worked with cn=config. The first two patches deal with that. The last patch introduces a new backend flag that indicates that it should be started up even if there is no database using it. IPR notice: The linked files are derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patches were developed Symas corp. Symas corp. has not assigned rights and/or interest in this work to any party. I, Ondrej Kuznik am authorized by Symas corp. to release this work under the following terms. Symas corp. hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

(ITS#8858) Walking the thread pool work queue
by ondra＠openldap.org 21 May '18

21 May '18

Full_Name: Ondrej Kuznik Version: master OS: URL: https://github.com/mistotebe/openldap/tree/ITS8858 Submission from: (NULL) (82.10.24.68) During reconfiguration, the load balancer might need to dispose of some resources (connections, ...) as the new configuration invalidates their state. Due to how pool pause is handled in libldap_r, tasks might still be queued in there that reference those objects and need to be de-queued before we resume. Most of the time, it is sufficient to record the cookie from pool_submit2 and use pool_retract. At least in some phases of the load balancer implementation we could have more than one task scheduled for the same object - with reconfiguration being the rare case, optimising for it at the expense of the common case does not feel right. The linked patch is ready for review, it lets the caller examine the tasks with a specified start_routine and have any of them retracted where appropriate.

1 0

Re: (ITS#8852) slapd memory use grows continuously with non-delta syncrepl and modifying groups
by hyc＠symas.com 19 May '18

19 May '18

ryan(a)nardis.ca wrote: > bisect identifies c365ac359e9c9b483b934c2a1f0bc552645c32fa as the commit > that introduced this behaviour. > > 003dfbda574f37bbf1a2240f530ff9fa35ab0801 on RE24 (2.4.20) > > commit c365ac359e9c9b483b934c2a1f0bc552645c32fa > Author: Howard Chu <hyc(a)openldap.org> > Date: Sun Nov 22 04:42:00 2009 +0000 > > ITS#6368 use dup'd entries in response queue I've run your reproducer and see no memory leak. The response queue will indeed grow without bound if the consumer runs slower than the provider, and doesn't read responses fast enough. But in the case of this test script, eventually the client finishes and the consumer catches up. The provider's process size may not decrease, but that just means the malloc implementation isn't returning freed memory to the kernel - it's not a leak. This can be verified using mleak, and using SIGPROF to snapshot the memory usage of the provider. The simplest way to force the memory use to grow is to first suspend the consumer with SIGSTOP. Let the modify client run to completion. mleak / SIGPROF will show a large amount of memory in use. Resume the consumer with SIGCONT, let it run to completion, and then check with SIGPROF on the provider again - all of the response queue memory is freed. So, conclusively, there is no actual leak. But there's a problem with sustained client modifications when the consumer is too slow. Our options here are to configure a size limit on the response queue, and hang the client when the limit is hit, or to return LDAP_BUSY to the client. Neither of these are very attractive options. Doing batched commits will speed up the consumer, but that feature is only in 2.5. -- -- 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

Re: (ITS#8846) Patch to introduce new LDAP option to ignore hostname checking while verifying certificates in TLS mode
by sudhir.singam＠gmail.com 16 May '18

16 May '18

--000000000000ef2539056c5164f5 Content-Type: text/plain; charset="UTF-8" Hi, Reference to SOAP, where we have the option of SOAP_SSL_SKIP_HOST_CHECK https://www.genivia.com/doc/soapdoc2.html --000000000000ef2539056c5164f5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi,<br><br>Reference to SOAP, where we have the option of= =C2=A0=C2=A0<span style=3D"color:rgb(0,0,0);font-family:inconsolatamedium,m= onospace,serif;font-size:14px;font-style:normal;font-variant-ligatures:norm= al;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-alig= n:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:= 0px;background-color:rgb(255,255,238);text-decoration-style:initial;text-de= coration-color:initial;float:none;display:inline">SOAP_SSL_SKIP_HOST_CHECK<= /span> <br><br><a href=3D"https://www.genivia.com/doc/soapdoc2.html">https://www.g= enivia.com/doc/soapdoc2.html</a><div><br></div><div><br><div><br></div></di= v></div> --000000000000ef2539056c5164f5--

1 0

Re: (ITS#8846) Patch to introduce new LDAP option to ignore hostname checking while verifying certificates in TLS mode
by sudhir.singam＠gmail.com 16 May '18

16 May '18

Hi, Thanks for the reply. For DNS use case, " Operator may make certificates only once in a while (as they cost), and at that point it is not certain that all IP addresses are known. They likely might now only know the current literal address, but the numeric address can change in the lifetime of the certificate Changing /etc/hosts is not possible, as this configuration is not supported for operators. " Still we feel configuration is a good thing, i.e., if one explicitly wants to allow a connection despite of warnings (i.e., has analysed the warning to be a false positive), that should still be acceptable, and not unilaterally bad. Also, one needs to be able to distinguish between =E2=80=9Cnormal=E2=80=9D network (open for everyone), and an operat= or-internal network: requirements for these two are different, and if one library is to serve both, it should be able to handle (=3Dbeing configurable) both use cases. System configuration setup is anyway also done by a human, so if someone wants explicitly disable some checks for automated clients, it is logically similar to a human pressing some =E2=80=9Cacknowledge=E2=80=9D= button. And i don't think the browsers are going to remove it, at most they may move this option to settings. I think nobody wants a monolithic browser that cannot be tailored for user needs, which anyway cannot be anticipated by the browser maker. Whether it is interactive or configuration based does not matter as long as the configuration is there somehow. And the same logic applies also for LDAP ;) But then openLDAP or openSSL is already providing options to ignore some of the certificate errors, for example, i can set SSL verify call back function via LDAP options to ignore certificate CRL errors and continue the connection. So i still wonder why it is not possible in this case and feel it has to be user configurable. Regards, Sudhir, NOKIA

1 0

(ITS#8846) Patch to introduce new LDAP option to ignore hostname checking while verifying certificates in TLS mode
by sudhir.singam＠gmail.com 16 May '18

16 May '18

--000000000000d6fc43056c4ba325 Content-Type: text/plain; charset="UTF-8" Hi, --000000000000d6fc43056c4ba325 Content-Type: text/html; charset="UTF-8" <div dir="ltr">Hi,</div> --000000000000d6fc43056c4ba325--

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs