Title: Message

Two questions:

1)       Can I see the line(s) of code that does(do) the bind?

2)       What is the timestamp and version number on the wldap32.dll that you’re calling?

 

With that I can probably track it down.

 

Thanks!

~Eric

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Thursday, March 24, 2005 7:39 AM
To: [email protected]
Subject: RE: [ActiveDir] LDAP NTLM Authed Channel Encryption Question was LDAPS part 2

 

That is exactly what I was thinking. I bounced it off Eric but he hasn't had a chance to look at it yet.

 

  joe

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, March 24, 2005 10:13 AM
To: [email protected]
Subject: RE: [ActiveDir] LDAP NTLM Authed Channel Encryption Question was LDAPS part 2

Doesn’t that smell like a bug or something?  This doesn’t seem to be the documented behavior.

 

Eric? J

 

We could bounce this off the SDK team too as they are responsible for the code.

 

Joe K.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Wednesday, March 23, 2005 9:29 PM
To: [email protected]
Subject: RE: [ActiveDir] LDAP NTLM Authed Channel Encryption Question was LDAPS part 2

 

No encrypt specified, in fact I can specifically set it to off (0) and it still encrypts. I can not get it to do anything clear text once it hits and succeeds the SASL NTLM bind.

 

  joe

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Reply via email to