Hi Marcel,

   It is about the security configuration of the domain controller. It can
be configured to only accept NTLMv2. The change is for non Windows_SSPI.

Thank you
Markus

-----Original Message-----
From: Marcel Raad
Sent: Tuesday, December 11, 2018 4:01 PM
To: libcurl development
Cc: Daniel Stenberg ; Markus Moeller
Subject: RE: NTLMV2 authentication;

> -----Original Message-----
> From: curl-library <curl-library-bounces_at_cool.haxx.se> On Behalf Of Daniel
> Stenberg via curl-library
> Sent: Dienstag, 11. Dezember 2018 12:40
> To: Markus Moeller via curl-library <curl-library_at_cool.haxx.se>
> Cc: Daniel Stenberg <daniel_at_haxx.se>; Markus Moeller
> <huaraz_at_moeller.plus.com>
> Subject: Re: NTLMV2 authentication;
>
> 2. Confirmation by one or two other users that NTLM still works. Since our
> test cases don't really know NTLM and just verify that we keep using it
> like
> before, we need to verify that this doesn't break existing behaviors
> against
> some actual NTLM end-points.

Sorry, I didn't follow the conversation completely even though I'm
interested
in the topic as I'm pretty busy currently.

What cases are we talking about? Only non-Windows / non-SSPI libcurl
clients,
right? I have access to some proxy servers in a Windows domain and I have
full
control over them, but I don't have access to the domain controller - is
that
enough or do I have to configure the NTLM flavors on the domain controller
(IIRC, I read that in a previous e-mail)?

Thanks,
Marcel

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-12-12