🚀 go-pugleaf

Hi all, I hope everybody is well and still happy'ish.  Things have been a
bit heated lately.

Just wondering if anybody had any experience or understanding of GINA
development.  I'm currently developing a GINAStub based on the VC++ code
example from Microsoft's Dev Studio.

I've re-created it in Builder and it seems to work ok.  However, my question
is a conceptual one and relates to the way Windows 'daisy-chains' the GINA's
that are installed.  A bit of back-ground I think :-)

From what I can tell from MSDN research, when Windows first starts up
Winlongon.exe is started / created.  This executable then examines the
registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon] to determine which GINA to load up.  When 'one'
wishes to create a gina-stub, we modify this value to point to our GINA i.e.
myGINA.dll.  When myGINA.dll starts up, to basically loads the original
value that was held in the above registry key (usually MSGINA.dll).  The
stub-gina, myGINA.dll then redirects / relays on all it's exported functions
on to this secondary gina, MSGINA.dll.

Now this is what I have created, however what I don't understand is this;
according to the repeater code below, when the user logons on throught the
normal logon interface, myGINA.dll's method, WlxLoggedOutSAS, is called and
all the relevant information is passed to it, this then relays it on to
MSGINA.dll's same function (we will call our pointer to it
GWlxLoggedOutSAS).  GWlxLoggedOutSAS then, within MSGINA.dll calls
LogonUser() to log the user on.

// declared / defined in Gina-Stub, myGINA.dll
int WINAPI WlxLoggedOutSAS(PVOID pWlxContext,
                                                    DWORD dwSasType,
                                                    PLUID pAuthenticationId,
                                                    PSID pLogonSid,
                                                    PDWORD
pdwOptions,
                                                    PHANDLE         phToken,
                                                    PWLX_MPR_NOTIFY_INFO
pMprNotifyInfo,
                                                   PVOID
*pProfile)
{
    int iRet;
    // calls the original method within MSGINA.dll etc
    iRet = GWlxLoggedOutSAS(
                pWlxContext,
                dwSasType,
                pAuthenticationId,
                pLogonSid,
                pdwOptions,
                phToken,
                pMprNotifyInfo,
                pProfile);


    if(iRet == WLX_SAS_ACTION_LOGON) {
        //
        // copy pMprNotifyInfo and pLogonSid for later use
        //

        // pMprNotifyInfo->pszUserName
        // pMprNotifyInfo->pszDomain
        // pMprNotifyInfo->pszPassword
        // pMprNotifyInfo->pszOldPassword


I don't understand this.  The logon dialog is within MSGINA.dll, the logon
information (username, password, domain etc) all originale from MSGINA.dll,
however my stub method WlxLoggedOutSAS appears to recieve the call and
relays it back on to MSGINA.dll.  I just don't understand this - MSGINA.dll
has no idea or information about myGINA.dll.

Thanks in advance,

Mike