Am 2014-09-28 um 14:53 schrieb Anton Kabakov:
> Hi,
> I'm running into a problem to use NTLM authentication for users with UTF-8 characters in username. This seems to be a known issue described in
> http://curl.haxx.se/docs/knownbugs.html , bug #75
>
> I tried to build CURL with UNICODE flag, but the issue was not resolved. Is there any instructions about what exactly need to be done to resolve this?
> I'm using Red Hat based 32 bit Linux server.

Anton,

you should always provide: OS, Compiler, curl version. First of all,
there aren't any UTF-8 characters, only Unicode ones. -DUNICODE won't
help, because this is intended for Windows only.

You may try to pass raw UTF-8 octets (codepoints U+0400 to U+04FF in
your case) and see whether libcurl passes them correctly or not because
the Unix build has a custom NTLM implementation.

Provide an ASCII dump of the NTLM token from Wireshark.

Edit: My idea won't work because of this:
https://github.com/bagder/curl/blob/master/lib/curl_ntlm_msgs.c#L531

NTLMFLAG_NEGOTIATE_OEM is passed. Bad stuff.

What you could do now is to swap this for NTLMFLAG_NEGOTIATE_UNICODE and
try the raw octets as advised.

С успехом,

Michael

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-09-28