From: Daniel Stenberg <daniel@haxx.se>
Date: Sat, 7 Jul 2012 12:38:50 +0000 (+0200)
Subject: KNOWN_BUGS: NTLM with unicode works with schannel/winssl!
X-Git-Tag: upstream/7.37.1~2799
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=5a99bce07dba1b79149deab9b8669793a6c22f2e;p=platform%2Fupstream%2Fcurl.git

KNOWN_BUGS: NTLM with unicode works with schannel/winssl!

Bug #75 updated with additional info, still remains for builds with
other backends.
---

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index cf8bfc2..e697173 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -17,10 +17,15 @@ may have been fixed since this was written!
   curl_easy_getinfo() to return a socket properly with the CURLINFO_LASTSOCKET
   option as for all other operating systems.
 
-75. NTLM authentication involving unicode user name or password.
+75. NTLM authentication involving unicode user name or password only works
+  properly if built with UNICODE defined together with the schannel/winssl
+  backend. The original problem was mentioned in:
   http://curl.haxx.se/mail/lib-2009-10/0024.html
   http://curl.haxx.se/bug/view.cgi?id=2944325
 
+  The schannel version verified to work as mentioned in
+  http://curl.haxx.se/mail/lib-2012-07/0073.html
+
 73. if a connection is made to a FTP server but the server then just never
   sends the 220 response or otherwise is dead slow, libcurl will not
   acknowledge the connection timeout during that phase but only the "real"