FYI: I'm only guessing that the non-SSPI build doesn't have the problem,
based solely on this comment (on the Microsoft web page referred in the
bug report, linked via tinyurl.com):

  "The CompleteAuthToken function completes an authentication token.
   This function is used by protocols, such as DCE, that need to
   revise the security information after the transport application
   has updated some message parameters.

  "This function is supported only by the Digest security support
   provider (SSP)."

I haven't actually done a build to test the theory.

- Kevin

-----Original Message-----
From: Daniel Stenberg
Sent: Monday, May 23, 2005 12:44 PM

On Mon, 23 May 2005, Roth, Kevin P. wrote:

> Or, could you perhaps provide a windows build of curl with SSPI turned
off
> (in addition to the current one of course)?

Aha, so the non-SSPI build didn't have this effect then?
Received on 2005-05-23