openldap-devel

openldap-devel@openldap.org

2 participants
1422 discussions

RE24 testing round 3
by Quanah Gibson-Mount 01 Sep '09

01 Sep '09

Please test. Thanks! --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

10 14

Fwd: Re: Plans for OpenLDAP 2.4?
by Howard Chu 31 Aug '09

31 Aug '09

Any thoughts on adding libldif as an installed library? I don't see it having any particular stability impact for our code, but it may give packagers a bit of heartburn if we add a new library in the middle of a release stream. re: MozNSS multi-init support - we have already been rolling the MozNSS code into RE24, but we've been omitting the configure switches for it because the code is still incomplete. Multi-init is one of the key features needed before this code will be safe for use by general applications. The issue of ciphersuite management still needs to be addressed as well. (The current code is usable, under very controlled circumstances...) -------- Original Message -------- Subject: Re: Plans for OpenLDAP 2.4? Date: Mon, 31 Aug 2009 15:38:17 -0600 From: Rich Megginson <rmeggins(a)redhat.com> Organization: Sec Eng (Directory Server) To: Howard Chu <hyc(a)symas.com> Howard Chu wrote: > Rich Megginson wrote: >> Do you have a date after which 2.4 branch development will be closed for >> new enhancements? We have 2 more features which we would like to get >> into OpenLDAP in order to be able to use it in our projects: >> 1) support for NSS multi-init - the guy working on this has a prototype >> working and has submitted the code to NSS upstream - no ETA yet >> 2) support for libldif >> >> How much time do we have in order to get these features into the 2.4 >> branch? > > It seems like we can add both of those without destabilizing any of > the existing code, so it should be OK. A 2.4.18 release candidate is > being tested now so it's probably too late for this cut. I'll raise > this question on the openldap-devel list. Ok. Thanks.

2 1

(no subject)
by masarati＠aero.polimi.it 26 Aug '09

26 Aug '09

Quanah, Re24 -> 2.4.18: you could also incorporate ITS#6260, ldap_get/set_option(3) (only affects doc/man/man3/ldap_get_option.3, including the documentation of ITS#6257). Thanks, p.

2 2

Two small wishes for 2.4.18
by Michael Ströder 25 Aug '09

25 Aug '09

HI! Since AFAIK 2.4.18 is still not tagged for release I'd like to suggest two things to add: 1. ITS#4730 slapo-allowed to be added under contrib/ with the Makefile I sent 2. ITS#6257 libldap: getopt flag to return the SASL username Any objections? Ciao, Michael.

1 1

RE24 testing for 2.4.18
by Quanah Gibson-Mount 24 Aug '09

24 Aug '09

Please test RE24. Thanks! --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

9 15

Re: commit: ldap/servers/slapd/overlays pcache.c
by masarati＠aero.polimi.it 21 Aug '09

21 Aug '09

> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays > > Modified Files: > pcache.c 1.193 -> 1.194 > > Log Message: > ITS#6152 add tests for cache refresh and Bind caching Valgrind is complaining about uninit'ed values in pcache configuration, and some leaks in cached entries. I might look at this later, no time right now. p.

1 0

Re: commit: ldap/servers/slapd/overlays pcache.c
by masarati＠aero.polimi.it 19 Aug '09

19 Aug '09

> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays > > Modified Files: > pcache.c 1.189 -> 1.190 > > Log Message: > more cache monitoring (ITS#5178) I'm just exposing counters. I see few inconsistencies, though. The number of pcacheQueryURL values corresponds to pcacheNumQueries, but the pcacheNumEntries seems quite erratic. Different executions of test020 report a number of cached entries ranging from 10 to 12. Searching the cache with the privDB control always returns 10 entries with pcacheQueryID=* in the cache. After cleanup, the counter in fact drops by 10, although the database is empty (apart from the glue entries, of course). p.

1 0

Re: commit: ldap/doc/man/man3 ldap_get_option.3
by Howard Chu 19 Aug '09

19 Aug '09

ando(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/doc/man/man3 > > Modified Files: > ldap_get_option.3 1.11 -> 1.12 > > Log Message: > document all options, including TLS and (not yet complete) SASL. Needs expert review I would drop LDAP_OPT_X_TLS; it basically turns on ldaps. This has been unnecessary ever since ldap_initialize() was provided and is only likely to cause problems. (E.g., URI says "ldap://" but library opens ldaps session -> massive confusion.) -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 1

Re: commit: ldap/doc/man/man3 ldap_get_option.3
by Howard Chu 19 Aug '09

19 Aug '09

ando(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/doc/man/man3 > > Modified Files: > ldap_get_option.3 1.11 -> 1.12 > > Log Message: > document all options, including TLS and (not yet complete) SASL. Needs expert review LDAP_OPT_X_TLS_CONNECT_CB / _ARG is implemented, but probably not useful. I used it to obtain the SSL session handle on a newly allocated session to insert it into the OpenSSL session cache. These days I would instead add generic hooks for enabling an implementation-specific session cache. -- -- 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

HAVE_GMTIME_R?
by masarati＠aero.polimi.it 19 Aug '09

19 Aug '09

The code is littered with tests like #ifdef HAVE_GMTIME_R, but there's no longer tests for gmtime_r() in configure. Is it time to cleanup a bit? p.

5 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel