configure \
--with-threads=posix \
--enable-local \
--enable-rlookups \
--with-tls=no \
--with-cyrus-sasl \
--enable-wrappers \
--enable-passwd \
--enable-cleartext \
--enable-crypt \
--enable-spasswd \
--disable-lmpasswd \
--enable-modules \
--disable-sql \
--libexecdir=%{_libdir}
build \
--enable-plugins \
--enable-slapd \
--enable-multimaster \
--enable-bdb \
--enable-hdb \
--enable-ldap \
--enable-ldbm \
--with-ldbm-api=%{ldbm_backend} \
--enable-meta \
--enable-monitor \
--enable-null \
--enable-shell \
--enable-sql=mod \
--disable-ndb \
--enable-passwd \
--enable-sock \
--disable-perl \
--enable-relay \
--disable-shared \
--disable-dynamic \
--with-kerberos=k5only \
--enable-overlays=mod
This is how redhat builds openldap; which are the bad libs? Are they the
lib crypt (--enable-crypt); what should I use instead?
Michele Masè
On Mon, May 21, 2012 at 11:47 PM, Quanah Gibson-Mount <[email protected]>wrote:
> --On Monday, May 21, 2012 11:40 PM +0200 Michele Mase' <
> [email protected]> wrote:
>
> Is it really bad? Is it buggy? Since redhat has its own ldap 389 dir.
>> server, I suppose they don't care of openldap. isn't it?
>> Michele Masè
>>
>
> There are known issues with the release they use, and the crypto libraries
> it is linked to.
>
>
> --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
>
