RE24 testing call (2.4.27 official call #3)
by Quanah Gibson-Mount
Please test latest RE24. dynamic config support for back-sql and back-perl
have been added. If anyone has a setup to test either of those
specifically, that would be useful.
Thanks,
Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
12 years
Channel bindings
by Howard Chu
Now that Cyrus SASL 2.1.25 is out with channel binding support, we should be
looking into adding the hooks needed to use it. I believe what we want to
expose is an ldap_get_option(ld, LDAP_OPT_X_TLS_BINDING, &foo) to retrieve the
tls-unique binding data from the underlying TLS session. Then we pass this
into SASL using sasl_setprop(ctx, SASL_CHANNEL_BINDING, foo). The actual
ldap_get_option() code will have to be added for each TLS implementation.
It seems pretty straightforward, am I missing anything?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
12 years
Re: RE24 testing call (2.4.27 official call #2)
by Marco Pizzoli
All tests passed with RE24 from 18Nov on RHEL6.1-64bit, compiled against
BDB 5.2.36.
Marco
On Thu, Nov 10, 2011 at 4:05 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote:
> Please test latest RE24. Thanks!
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Sr. Member of Technical Staff
> Zimbra, Inc
> A Division of VMware, Inc.
> --------------------
> Zimbra :: the leader in open source messaging and collaboration
>
>
--
_________________________________________
Non è forte chi non cade, ma chi cadendo ha la forza di rialzarsi.
Jim Morrison
12 years
What to do with test058?
by Ralf Haferkamp
Hi,
I wonder how we should go forward with test058-syncrepl-asymmetric. If I
understand the test (and the comments in syncrepl.c) correctly the setup
it is testing is unsupported in slapd, am I right? (Which is the reason
why test failures are ignored currently, I guess)
On the provider the syncprov overlay is setup for the glued database and
the consumer's syncrepl clients (also glued) are configured on the
individual child databases. Additionally the consumers have configure the
the syncprov overlay also of the topmost database. AFAICS all of the
failures that test058 reports are related to this unsupported config.
Is anybody planning to work on adding support for such a setup. Or should
we just rework the test to a supported scenario (or even remove it
completely)?
Ralf
12 years
MDB name
by Howard Chu
What's in a name... Apparently "MDB" is already a well-known suffix for
Microsoft Access database files. "mdb" is also the name of a debugger tool in
Solaris. To avoid confusion with those unrelated items, it might be a good
idea to rename our MDB to something else. Now, before the next OpenLDAP
release is published. Comments?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
12 years
drop "stable"
by Michael Ströder
HI!
Many people are downloading and compiling "stable" releases from
http://www.openldap.org/software/download/ which is IMO problematic:
Most developers consider those "stable" releases to be rather outdated since
lots of fixes are missing and they don't want to get bothered with old issues
(which I personally perfectly understand). ITS filed against those "stable"
versions are most times answered like "get a more recent release".
There is no well-defined process how to determine whether a release has
reached "stable" status.
=> My suggestion: Simply drop "stable" completely and list only the releases
with version number without further qualification. Today most people can deal
with version numbers quite well.
Ciao, Michael.
12 years
RE24 testing (pre-testing on 2.4.27)
by Quanah Gibson-Mount
Tomorrow I'll be working on merging in libmdb/back-mdb. If anyone would
like to do a basic sanity test against current RE24, that would be helpful.
It has all of the planned fixes for 2.4.27 except ITS#7025 which Howard is
still working on.
Thanks!
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
12 years
RE24 testing call (2.4.27 official call #1)
by Quanah Gibson-Mount
Please test RE24. Thanks!
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
12 years
RE24 testing call (2.4.27 official call #2)
by Quanah Gibson-Mount
Please test latest RE24. Thanks!
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
12 years
Note on Cyrus-SASL when testing
by Quanah Gibson-Mount
Latest cyrus-sasl 2.1.25 introduces a new mechanism called SCRAM. Unlike
the other mechanisms, SCRAM generates entropy as soon as the cyrus-sasl
library is loaded. This is a problem because cyrus-sasl defaults to using
/dev/random instead of /dev/urandom when it loads up. I was having
numerous test failures until gdb'ing slapd and finding it was stuck
initializing SCRAM while starting up.
If you rebuild cyrus-sasl to use /dev/urandom (They thankfully have a
configure switch for it), things'll work a lot more smoothly.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
12 years, 1 month
