[Date Prev][Date Next]
AW: Problems with ldapwhoami -> slapd -> segmentation fault
> -----Ursprüngliche Nachricht-----
> Von: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org] Im Auftrag von
> Quanah Gibson-Mount
> Gesendet: woensdag 25 augustus 2004 18:20
> An: Guus Leeuw jr.; OpenLDAP-software@OpenLDAP.org
> Betreff: Re: Problems with ldapwhoami -> slapd -> segmentation fault
> --On Wednesday, August 25, 2004 8:12 AM +0200 "Guus Leeuw jr."
> <Guus-Leeuw@gmx.de> wrote:
> > Hi all,
> > I don?t really know whether the question actually belongs
> here (*it*
> > seems to be indicating a problem in the Cyrus SASL arena), but then
> > again, the problem only shows with slapd (2.2.15 and cvs HEAD).
> > Following is the situation:
> > I set up db4 from source+patches, OpenSSL 0.9.7d, MIT krb5 on top,
> > then I compiled Cyrus SASL, and took 3 weeks to figure out what the
> > hell was wrong with the saslauthd (it would always say NO, until I
> > figured, I have the wrong service/FQDN pair in the keytab). So that
> > worked, and I happily progressed on to OpenLDAP.
> I suggest reading the list archives for "MIT" and "Heimdal"
> to see why you
> probably do not want to use MIT Krb5 on top, and should
> instead use Heimdal.
Yeah, I might try that one day... ;)
I'm not too sure though, the problem is with MIT...
I rather think the problem is somehow with SASL&slapd or slapd by
itself... Slapd really seems to think (by the sasl2 lib, that it
should open /etc/sasldb2 (which has no use in case of GSSAPI...
Or so the manpage says...) So I guess I am missing some kind of
Configuration to this piece or that piece (not slapd.conf, since
that one seems to go for SASL2... ;)
*but* the sample-server and sample-client work together upto the point
Where the client says: Expecting encrypted message (which it says after
It reports authentication OK). Also the saslauthd and testsaslauthd indicate
OK, so I think SASL is not really off...
Must be somthing in slapd then?
In which function is the session_callbacks array actually used? Maybe it
Not traverse well enough... And skips the SASL_CB_LIST_END id? (Wild guess!)
Anything else you can think of, Quanah? (and others ;)
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004