[01/10] secur32: Implement AcquireCredentialsHandle for Kerberos.
dmitry at baikal.ru
Thu Oct 19 21:51:40 CDT 2017
Hans Leidekker <hans at codeweavers.com> wrote:
> On Mon, 2017-10-16 at 17:55 +0800, Dmitry Timoshkov wrote:
> diff --git a/wine/dlls/kerberos/kerberos.spec b/wine/dlls/kerberos/kerberos.spec
> > diff --git a/wine/dlls/kerberos/kerberos.spec b/wine/dlls/kerberos/kerberos.spec
> > index d277cee..e92516f 100644
> > --- a/wine/dlls/kerberos/kerberos.spec
> > +++ b/wine/dlls/kerberos/kerberos.spec
> > @@ -1 +1,3 @@
> > @ stdcall SpLsaModeInitialize(long ptr ptr ptr)
> > +@ stdcall InitSecurityInterfaceA()
> > +@ stdcall InitSecurityInterfaceW()
> The Windows 10 version doesn't export these functions. It does export a
> SECPKG_USER_FUNCTION_TABLE via SpUserModeInitialize but that doesn't give
> us everything we need.
It looks like MSDN suggests that both SECPKG_FUNCTION_TABLE (returned by
SpLsaModeInitialize) and SECPKG_USER_FUNCTION_TABLE (returned by SpUserModeInitialize)
should be used for an SSPI:
Since this requires quite a bit of changing to secur32 SSP management code
I'd suggest to simply add two above exports for now.
More information about the wine-devel