[Date Prev][Date Next]
Re: SASL/GSSAPI with 2.1.4 causes segfaults
Suggest you file a bug report with appropriate details.
Aside from the information in this post, a stack back
trace (with symbols) would be useful. If threaded,
a trace of the thread which generated the segfault.
At 03:53 PM 2002-08-29, Quanah Gibson-Mount wrote:
>473180.jpg Re SASLGSSAPI with 2.1.4 caus.ems<file://c:\home\kurt\data files\eudora\attach\Re SASLGSSAPI with 2.1.4 caus.ems <0880.0002>>
>*** PGP Signature Status: unknown
>*** Signer: Unknown, Key ID xC99D8A8B
>*** Signed: 2002-08-29 3:53:30 PM
>*** Verified: 2002-08-29 4:19:54 PM
>*** BEGIN PGP VERIFIED MESSAGE ***
>--On Thursday, August 29, 2002 2:28 PM -0700 Quanah Gibson-Mount <quanah@Stanford.EDU> wrote:
>>I'm wondering if anyone else has seen the following problem with 2.1.4.
>>Berkeley DB 4.0.14
>>I upgraded my installation from 2.1.3 leaving the rest the same, and now
>>every time I try to do a K5 bind (which worked flawlessly under 2.1.3),
>>it seg faults. Note that the database was deleted, so as to start fresh.
>>I then import the initial part of our database. Using ldapsearch -x
>>works without problem. ldapsearch with GSSAPI results in:
>Resolution on this:
>Some change was made in OpenLDAP-2.1.4 that completely broke my previous regexps that worked fine in 2.1.3. So at this point, I don't know if that is a bug with the new code that was put in, or a 'feature' of 2.1.4 that I'll need to go and figure out if my regexp's will even work with 2.1.4. They were quite simple regexps to boot.
>sasl-regexp uid=(.*),cn=(.*),cn=gssapi,cn=auth ldaps:///cn=People,dc=stanford,dc=edu??sub?(|(krb5PrincipalName=$1@$2)(suKr
>completey kills slapd now, for example.
>Senior Systems Administrator
>GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
>*** END PGP VERIFIED MESSAGE ***