KNOWN_BUGS: SHA-256 digest not supported in Windows SSPI builds

Closes https://github.com/curl/curl/issues/6302

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 3726f41531f6f30c2e9995c8e74395147dd5cf6f..9013577a2953a16bdaa239d8633bfb0558c614b0 100644 (file)
--- 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