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
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
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
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
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
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
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
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
steffen(a)sdaoden.eu wrote:
> Full_Name: Steffen Nurpmeso
> Version: 0.9.23
> OS: Linux
> URL: https://ftp.sdaoden.eu/lmdb-bogo.tar.xz
> Submission from: (NULL) (109.40.130.211)
>
>
> A follow-up to private communication with Quanah Gibson-Mount.
> You can find more in the tarball linked below.
The code works as designed. No changes to mapsize handling were made between 0.9.22 and 0.9.23.
Closing this ITS.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
steffen(a)sdaoden.eu wrote:
> Full_Name: Steffen Nurpmeso
> Version: 0.9.23
> OS: Linux
> URL: https://ftp.sdaoden.eu/lmdb-bogo.tar.xz
> Submission from: (NULL) (109.40.130.211)
>
>
> A follow-up to private communication with Quanah Gibson-Mount.
> You can find more in the tarball linked below
>
>
Your README states that the behavior in LMDB 0.9.23 is different than in 0.9.22 but that
is incorrect. No changes to set_mapsize() behavior were made between 0.9.22 and 0.9.23.
Closing this ITS.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/