openldap-bugs June 2019

openldap-bugs@openldap.org

27 participants
104 discussions

Re: (ITS#8671) Declare ldap_init_fd() in ldap.h to help external consumers
by abokovoy＠redhat.com 14 Jun '19

14 Jun '19

On pe, 14 kesä 2019, Ondřej Kuzník wrote: >On Thu, Oct 19, 2017 at 03:39:24PM +0000, quanah(a)symas.com wrote: >> --On Thursday, October 19, 2017 10:20 AM +0300 Alexander Bokovoy >> <abokovoy(a)redhat.com> wrote: >>> Hi Quanah, >>> >>> On ti, 12 syys 2017, Quanah Gibson-Mount wrote: >>>> Hi Alexander, >>>> >>>> Your submission appears to be missing an IPR statement as noted at >>>> <https://www.openldap.org/devel/contributing.html#notice>. This is >>>> required for your submission to be evaluated. Please add an IPR at >>>> your earliest convenience. >>> Attached is a re-based patch set since there were changes in git master >>> in last month or so that affected the same area. >>> >>> There are two patches: one for git master, one for 2.4 branch. Since >>> there is no functional change in the code, I'd like to see the 2.4 >>> version in an upcoming release as that would greatly help Samba. >>> >>> I'm also including an IPR notice below: >>> >>> Red Hat, Inc. 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. >> >> Thanks very much! I'll get this into my scratch repo for review. > >Hi Alexander, >as of commit 6a5e30674b63b17587738ba9a3d1ea3633c33fb1, OpenLDAP master >now ships and installs a new header <openldap.h> that should expose >ldap_init_fd(). Could you check this will work for Samba before we apply >this change in 2.4? Thanks. I've compiled openldap git master and installed it, I can see $prefix/include/openldap.h with ldap_init_fd() and man pages have proper references to openldap.h. Looks good to me. Once 2.4 becomes available, we can add support of this to Samba. -- / Alexander Bokovoy Sr. Principal Software Engineer Security / Identity Management Engineering Red Hat Limited, Finland

1 0

Re: (ITS#8671) Declare ldap_init_fd() in ldap.h to help external consumers
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Thu, Oct 19, 2017 at 03:39:24PM +0000, quanah(a)symas.com wrote: > --On Thursday, October 19, 2017 10:20 AM +0300 Alexander Bokovoy > <abokovoy(a)redhat.com> wrote: >> Hi Quanah, >> >> On ti, 12 syys 2017, Quanah Gibson-Mount wrote: >>> Hi Alexander, >>> >>> Your submission appears to be missing an IPR statement as noted at >>> <https://www.openldap.org/devel/contributing.html#notice>. This is >>> required for your submission to be evaluated. Please add an IPR at >>> your earliest convenience. >> Attached is a re-based patch set since there were changes in git master >> in last month or so that affected the same area. >> >> There are two patches: one for git master, one for 2.4 branch. Since >> there is no functional change in the code, I'd like to see the 2.4 >> version in an upcoming release as that would greatly help Samba. >> >> I'm also including an IPR notice below: >> >> Red Hat, Inc. 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. > > Thanks very much! I'll get this into my scratch repo for review. Hi Alexander, as of commit 6a5e30674b63b17587738ba9a3d1ea3633c33fb1, OpenLDAP master now ships and installs a new header <openldap.h> that should expose ldap_init_fd(). Could you check this will work for Samba before we apply this change in 2.4? Thanks, -- 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#9020) Inconsistent cn=config objectClasses for overlays
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Thu, May 09, 2019 at 04:21:56PM +0000, quanah(a)openldap.org wrote: > The majority of supported overlays use an objectClass of the format: > > olcOVERLAYConfig > > However, there are two overlays that do *not* follow this format, which is > confusing. > > memberOf -> olcMemberOf > dynlist -> olcDynamicList > > For 2.5, I would suggest we change these to be consistent with all the other > overlays and document this change in the Admin Guide section on upgrade notes > etc. Maybe we could change the name in 2.4 with the proposed names as the primary keeping the old one as an alternative? Don't remember if slapcat would translate them accordingly. If it does, we could just drop the old name in 2.5 (and have everyone slapcat cn=config with OpenLDAP >= 2.4.48 or wherever this lands). Or just do the above in 2.5 only. -- 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#8754) ldpasearch IPv5 only
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Wed, Oct 11, 2017 at 12:24:56PM +0000, dpa-openldap(a)aegee.org wrote: > After `./configure --disable-ipv6` I expect, that `ldapsearch` will not contact > severs over IPv6, which is achieved with the fix below. Hi, thank you for your work, the patch has been pushed to master (5e8aa3f6d111160cbb3ce3a49af7323258e702b5) and will also be part (c4f55cea87880ca8c14b559bd77bcea19ad615cd) of the upcoming 2.4.48 release. Thanks, -- 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#8427) Incorrect value of tls_reqcert in syncrepl
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Fri, Dec 01, 2017 at 07:15:08PM +0000, mkp37215(a)gmail.com wrote: > I, Maciej Puzio, hereby place the above 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. Hi Maciej, thank you for your work, patches have been pushed to master and will also be part of the upcoming 2.4.48 release. Thanks, -- 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#8674) Leak in ldap_create_assertion_control
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Thu, Sep 07, 2017 at 03:42:50PM +0000, come(a)opensides.be wrote: > Hello, > > I encountered this bug as well while adding controls support into > php-ldap (see https://github.com/php/php-src/pull/2640 - WIP) > I used the work-around but it would still be better to fix this in > openldap. Hi Côme, thank you for your work, your patch has been pushed to master (2cac3ceb03530e3afe741d4a7d4d7e21059a6a97) and will also be part (8e6d1b8b81e94f89027a120ea862bd5938e953c6) of the upcoming 2.4.48 release. Thanks, -- 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#8167) The new non-blocking TLS connect does not work in a reference/referral
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Wed, Jun 10, 2015 at 12:39:19AM +0000, ipuleston(a)SonicWALL.com wrote: > I've now uploaded the patch to the ftp.openldap.org FTP server as "ian-pule= > ston-15069.patch". Hi Ian, thank you for your work, the patch has been pushed to master (46c93e41f43da7f16270179c6eff75e450617329) and will also be part (a8cf2fb10047794c83873f5ff5c125ecd0e53168) of the upcoming 2.4.48 release. Thanks, -- 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#8450) race condition in ldap_int_utils_init
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Fri, Jun 24, 2016 at 08:04:27PM +0000, doug.leavitt(a)oracle.com wrote: > There is a race condition in ldap_int_utils_init that can be triggered when > multiple threads enter ldap_int_utils_init from ldap_init_initialize about the > same time. The done flag gets set immediately, before the various mutexes are > initialized. If thread A sets done, and thread B tests for done==1 before thread > A has completed the mutex inits, thread B can attempt to use an uninitialized > mutex and fail/core dump etc. > > Additionally if judt the done=1 is moved to the bottom of the function thwo > threads can both be initializing the same mutexes multiple times causes other > mayhem. > > The short term workaround for Solaris (THR APIs) is to move setting of done=1 to > after the mutex inits, and to protect the mutex inits using another statically > initialized mutex within ldap_int_utils_init. Hi Doug, a patch addressing this and ITS#7996 has been pushed to master (db40120a276c3b7968552e253aea24860fad5f60) and will also be part (cde56fad154fcd25e351c3cd84d8173d263b0a01) of the upcoming 2.4.48 release. Thanks, -- 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#7996) Global initialisation race in ldap_int_initialize
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Fri, Sep 08, 2017 at 02:07:19PM +0000, quanah(a)symas.com wrote: > --On Friday, September 08, 2017 1:02 PM +0000 a.cudbardb(a)freeradius.org > wrote: >>> Thanks for the report and sorry for the delay on getting to this >>> issue. I would note that for the fix to be included in the OpenLDAP >>> project, we need an IPR statement, as noted at >>> <https://www.openldap.org/devel/contributing.html>. If you can >>> provide that, and (if possible) submit the patch as git format-patch >>> via the project FTP server (include the URL in your email), then I >>> can pull it in. >> >> IPR statement is not a problem, but I don't have the original diff to = >> work from. If you can send me a copy of the FTP submission I can = >> reformat it and resubmit it. > > Hi Arran, > > The diff is in your github issues tracker. ;) > > <https://github.com/arr2036/ldapperf/issues/2#issuecomment-66242732> Hi Arran, thank you for your work, a patch addressing this has been pushed to master (db40120a276c3b7968552e253aea24860fad5f60) and will also be part (cde56fad154fcd25e351c3cd84d8173d263b0a01) of the upcoming 2.4.48 release. Thanks, -- 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#7042) [PATCH] allow unsetting of tls_* options for syncrepl
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Sat, Oct 21, 2017 at 03:50:48PM +0000, patrick(a)monnerat.net wrote: > Hi Quanah, > Thanks for your directives and future action. Hi Patrick, thank you for your patch, it has now been pushed to master (0f9afae02d9425e54f070ecd5ea8b954115e092b) and will also be part (e5f945bab40482e2045fede3fbe9a04210808a93) of the upcoming 2.4.48 release. Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs June 2019