http://bugs.winehq.org/show_bug.cgi?id=19144
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |juan_lang@yahoo.com
--- Comment #3 from Juan Lang juan_lang@yahoo.com 2009-08-05 15:22:15 --- -2146893048 is 0x80090308, SEC_E_INVALID_TOKEN. I'm not sure where that's coming from, as schannel.c never returns it.
Could you patch secur32 as you propose, and attach a +secur32 log with that change? That'll at least help us identify if returning 1 is what the application is expecting.
Or, the best thing you could do is to write some tests for QueryContextAttributes. MSDN says QueryContextAttributes returns 0 on success, nonzero on failure, whereas some sample code on MSDN checks the return value with the FAILED macro. The FAILED macro only applies to HRESULTs, and any non-negative value "passes" with an HRESULT. A test would show what native secur32/schannel returns for SECPKG_ATTR_STREAM_SIZES, as well as what values it puts into the returned SecPkgContext_StreamSizes structure.