RE: Basic SASL setup instructions

["Howard Chu" <hyc@highlandsun.com>]

I've submitted a bug report on Netscape's web site. I missed some of the
details
you mentioned. Perhaps you should submit one as well with your findings.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Jim Hud
> Sent: Wednesday, October 18, 2000 3:58 PM
> To: Howard Chu; Kurt D. Zeilenga
> Cc: openldap-software@OpenLDAP.org
> Subject: Re: Basic SASL setup instructions
>
>
> My 10 cents.
>
> If you configure Netscape for SSL and login and then do not enter anything
> in the login prompt box it fails with 0x61.
>
> If you configure for SSL but no login it does not fail.
>
> BUT The verbose log from slapd shows exactly the same sequence, the TLS
> write is sending exactly the same sequence of bytes.
>
> Timing is one possibility but it is still down to Netscape.
>
>
>
> ----- Original Message -----
> From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
> To: "Howard Chu" <hyc@highlandsun.com>
> Cc: "Jim Hud" <jdhz@btinternet.com>; <openldap-software@OpenLDAP.org>
> Sent: Wednesday, October 18, 2000 8:53 PM
> Subject: RE: Basic SASL setup instructions
>
>
> > At 08:11 AM 10/18/00 -0700, Howard Chu wrote:
> > >Clearly there's something wrong with their BER decoding when SSL is in
> use.
> >
> > The problem appears to be a buffer offset problem between the client's
> > BER and TLS layers.  I'd have to look at it more carefully to determine
> > whether the octets are getting dropped or extra octets are getting
> > added between the layers.  In any case, it's looks like a Netscape
> > bug and should be reported to Netscape through appropriate channels.
> >
> > Kurt
> >
> >
>