[PATCH 8/9] kerberos: Don't include GSS_C_DCE_STYLE in default gss_init_sec_context() flags.

[Dmitry Timoshkov]

Hans Leidekker <hans at codeweavers.com> wrote:

> > Could you please provide the test sources along with the following log:
> > KRB5_TRACE=/dev/stdout WINEDEBUG=+secur32 wine yourtest.exe
> 
> Attached log is from runnning this command with your debug patch applied:
> KRB5_TRACE=/dev/stdout WINEDEBUG=+secur32,+kerberos ../../../tools/runtest -P wine -T ../../.. -M secur32.dll -p secur32_test.exe.so kerberos

Thanks. From the log:

0009:trace:kerberos:kerberos_SpSealMessage (7c623a20 0x00000000 0x32fc64 0)
0009:trace:kerberos:kerberos_SpSealMessage gss_wrap_iov returned 000d0000 minor status 00000016
0009:trace:kerberos:trace_gss_status_ex GSS-API error: 0x000d0000: "Unspecified GSS failure.  Minor code may provide more information"
0009:trace:kerberos:trace_gss_status_ex GSS-API error: 0x00000016: "Invalid argument"

Looks like gss_wrap_iov() depends on GSS_C_DCE_STYLE being provided at
the context creation time. That's weird, I can't find an explanation
that this flag is required for this API.

Did you test kerberos+secur32 patches with Kerberos Authentication Tester
in your kerberos testing environment?

-- 
Dmitry.