[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: change related to its 4046 seems to break sasl/gssapi working with AD

quite correct, 4064...  sorry about that.
ITS submitted.

-----Original Message-----
From: Quanah Gibson-Mount [mailto:quanah@stanford.edu]
Sent: Wednesday, October 19, 2005 6:01 PM
To: OpenLDAP software list
Cc: Chapman, Kyle
Subject: Re: change related to its 4046 seems to break sasl/gssapi
working with AD

--On Wednesday, October 19, 2005 2:20 PM -0700 Howard Chu <hyc@symas.com> 

> Quanah Gibson-Mount wrote:
>> --On Wednesday, October 19, 2005 3:13 PM -0400 "Chapman, Kyle"
>> <Kyle_Chapman@G1.com> wrote:
>>> im not sure this is a legit problem or an issue with how MS deals with
>>> sasl/gssapi...
>>> changes for cyrus.c to break sasl/gssapi binds to AD
>>> (vers 2.3.8 and up, at least for me).  if i roll back to in
>>> 2.3.11, everything builds ok and ldapsearch/sasl/gssapi to AD work.
>>> looking at the diff, there is memory cleanup as well as some changes to
>>> checking the values provided by scred following a call to
>>> ldap_sasl_bind_s.  adding back in the mem cleanup and the first reorder
>>> of the if statements and rebuilding, sasl/gssapi still works.   changing
>>> the second if statement results in (this change is after seeing if
>>> the rc
>>> and saslrc are OK):
>> You should follow up to the ITS if you want anyone to look at this.
>> Posts to the openldap-software list are seen as purely informational.
> ITS#4046 doesn't seem to be the right number.

Looks like maybe 4064?


Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html 
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.