[Date Prev][Date Next]
Re: OpenSSL + Kerberos + Cyrus-SASL + OpenLDAP
I may be wrong, but the last time I tried to compile heimdal-0.6 with BDB
support it failed since heimdal 0.6 uses the calls from the old bdb API to
access the database and since I am using the latest BDB 4.1.25 I
could not add bdb support to heimdal. I have a special
compile of bdb-4.1.25, heimdal-0.6, sasl-2.1.15 and openldap 2.1.22 on
/opt/local on my openldap server (running on solaris 9). My kerberos
server is MIT and I use the native ldap clients from solaris and red hat
to be ldap clients. (I finally got autofs working on both Redhat and
Solaris 9 :).
A recommendation to the guy that started this thread, is to use encap so
that he can swap versions easily in the future when new releases come out.
You may find about encap at http://www.encap.org
Diego Julian Remolina
School of Mathematics
Georgia Institute of Technology
On Mon, 13 Oct 2003, Quanah Gibson-Mount wrote:
> --On Monday, October 13, 2003 3:44 PM -0400 Igor Brezac <email@example.com>
> >> The build order I use is:
> >> OpenSSL
> >> Heimdal
> >> Cyrus-SASL
> >> Berkeley BDB
> >> OpenLDAP
> > Cyrus-sasl and Heimdal depend on Berkeley BDB. Berkeley BDB should be
> > compiled before Heimdal and Cyrus-SASL. Cyrus-SASL, OpenLDAP and Heimdal
> > potentially (depending on the compile options) depend on each other, so
> > you may need to compile each several times.
> That is not true. It depends on what/how you are using sasl & heimdal for.
> If you already have a KDC, there is no reason to build BDB before heimdal.
> And I see no reason to build it before building SASL if you aren't using
> their DB proxy pieces, which I'm not.
> Quanah Gibson-Mount
> Principal Software Developer
> ITSS/TSS/Computing Systems
> ITSS/TSS/Infrastructure Operations
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html