From 9f85b986a921cd3a46a7658c3a0e50d0d3a8e38d Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Mon, 14 Dec 2020 01:08:15 -0500 Subject: KNOWN_BUGS: SHA-256 digest not supported in Windows SSPI builds Closes https://github.com/curl/curl/issues/6302 --- docs/KNOWN_BUGS | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 3726f4153..9013577a2 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -70,6 +70,7 @@ problems may have been fixed or changed somewhat since this was written! 6.6 libcurl can fail to try alternatives with --proxy-any 6.7 Don't clear digest for single realm 6.8 RTSP authentication breaks without redirect support + 6.9 SHA-256 digest not supported in Windows SSPI builds 7. FTP 7.1 FTP without or slow 220 response @@ -558,6 +559,17 @@ problems may have been fixed or changed somewhat since this was written! See https://github.com/curl/curl/pull/4750 +6.9 SHA-256 digest not supported in Windows SSPI builds + + Windows builds of curl that have SSPI enabled use the native Windows API calls + to create authentication strings. The call to InitializeSecurityContext fails + with SEC_E_QOP_NOT_SUPPORTED which causes curl to fail with CURLE_AUTH_ERROR. + + Microsoft does not document supported digest algorithms and that SEC_E error + code is not a documented error for InitializeSecurityContext (digest). + + https://github.com/curl/curl/issues/6302 + 7. FTP 7.1 FTP without or slow 220 response -- cgit v1.2.1