mirror of
https://github.com/curl/curl.git
synced 2026-04-14 22:31:41 +03:00
NTLM_WB: drop support
The feature has not worked for months and has been marked as DEPRECATED for six+ months. Closes #13249
This commit is contained in:
parent
9e848439d8
commit
50def7c881
21 changed files with 25 additions and 723 deletions
|
|
@ -12,21 +12,6 @@ email the
|
|||
as soon as possible and explain to us why this is a problem for you and
|
||||
how your use case cannot be satisfied properly using a workaround.
|
||||
|
||||
## NTLM_WB auth
|
||||
|
||||
This NTLM authentication method is powered by a separate tool,
|
||||
`ntlm_auth`. Barely anyone uses this method. It was always a quirky
|
||||
implementation (including fork + exec), it has limited portability and we do
|
||||
not test it in the test suite and CI.
|
||||
|
||||
We keep the native NTLM implementation.
|
||||
|
||||
Due to a mistake, the `NTLM_WB` functionality is missing in builds since 8.4.0
|
||||
(October 2023). It needs to be manually patched to work. See [PR
|
||||
12479](https://github.com/curl/curl/pull/12479).
|
||||
|
||||
curl removes the support for NTLM_WB auth in April 2024.
|
||||
|
||||
## space-separated `NOPROXY` patterns
|
||||
|
||||
When specifying patterns/domain names for curl that should *not* go through a
|
||||
|
|
@ -56,3 +41,4 @@ curl removes the support for space-separated names in July 2024.
|
|||
- NSS
|
||||
- gskit
|
||||
- mingw v1
|
||||
- NTLM_WB
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue