| commit | b8f0649851f5ed59b7a333f0e915be1b786fc5c5 | |
| author | Dmitry Timoshkov <dmitry@baikal.ru> | |
| Mon, 5 Feb 2018 04:49:16 +0000 (5 12:49 +0800) | ||
| committer | Alexandre Julliard <julliard@winehq.org> | |
| Mon, 5 Feb 2018 10:46:45 +0000 (5 11:46 +0100) | ||
| tree | 308680f559e8f377b149000f8b7cc667f8e55dfa | treesnapshot (tar.gz zip) |
| parent | c03b41c8960335dbe4dfefb1118da872328c5b57 | commitdiff |
kerberos: Calling InitializeSecurityContext without a token buffer is not an error.
This patch makes Kerberos Authentication Tester work with https and dotnet40.
Apparently that's a dotnet40 quirk that it passes not NULL input buffers
but doesn't mark any of buffers as a token, dotnet20 passes NULL input.
Note, that in order to make version 2.0 applications work (Kerberos
Authentication Tester is such an application) with dotnet40+ one
needs to add to the registry key
[Software\\Microsoft\\.NETFramework]
"OnlyUseLatestCLR"=dword:00000001
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>
Signed-off-by: Hans Leidekker <hans@codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
This patch makes Kerberos Authentication Tester work with https and dotnet40.
Apparently that's a dotnet40 quirk that it passes not NULL input buffers
but doesn't mark any of buffers as a token, dotnet20 passes NULL input.
Note, that in order to make version 2.0 applications work (Kerberos
Authentication Tester is such an application) with dotnet40+ one
needs to add to the registry key
[Software\\Microsoft\\.NETFramework]
"OnlyUseLatestCLR"=dword:00000001
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>
Signed-off-by: Hans Leidekker <hans@codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
| dlls/kerberos/krb5_ap.c | diffblobblamehistory |