CryptoFun

Hi Nicholas,

Thanks for the good suggestion.

It looks like the hot fix I mentioned doesn't actually correct the problem
so it still appears to be a bug!

Thanks and Regards,
CryptoFun


"Nicholas Paldino [.NET/C# MVP]" wrote:

> Have you gone to the Microsoft Connect site and filed a bug? That site
> is tied directly into the bug system at MS, so if you put it there, you will
> have a MUCH better chance of a set of eyes getting on it that can actually
> make a change.
>
> Once you set up the case (or find one and verify it) you can post the
> link to have others weigh in on it as well.
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - mvp@spam.guard.caspershouse.com
>
> "CryptoFun" <CryptoFun@discussions.microsoft.com> wrote in message
> news:784C9FBC-7234-4D8F-BB33-38E43BAF4D00@microsoft.com...
> > Hi,
> >
> > There is a problem in 'System.Directory.Protocols' using the
> > LDAPSessionOptions function StartTransportSecurityLayer when using it with
> > an
> > openLDAP server.
> >
> > The call works fine with Active Direcotory on port 389 were the call
> > initiates a 'startTLS' LDAP command that starts TLS on the normally clear
> > port 389.
> >
> > Unfortionately when this is used with an openLDAP server the LDAP
> > 'startTLS'
> > command fails.
> >
> > This issue has been documented at the openLDAP site and is described at:
> > http://www.openldap.org/lists/openld.../msg00096.html
> >
> > There is a change that can be made to openLDAP source code file
> > 'starttls.c'
> > that will solve the problem but the protocol problem is actually on the
> > Microsoft side.
> >
> > There was also apparently a Microsoft hotfix for this issue on XP, windows
> > 2000 and Windows 2003 which is located at:
> >
> > http://support.microsoft.com/kb/841461/
> >
> > it is titled 'An extended operation that is sent to an LDAP server by API
> > over the LDAP service causes a protocol error'.
> >
> > The problem is that this same issue is occuring in the .NET
> > 'System.Directory.Protocols' using the LDAPSessionOptions function
> > StartTransportSecurityLayer when using it with an openLDAP server.
> >
> > It looks like the problem may have been fixed in pre .NET code but not in
> > .NET.
> >
> > Does anyone know if this will be corrected or if there is a Microsoft fix
> > for the .NET code?
> >
> > Thanks and Regards,
> > CryptoIsFun
> >
> >
> >
>