RE: Dialog box with GINA

From: Nick (Nick_at_discussions.microsoft.com)
Date: 05/11/05

  • Next message: Eric Slesar [MS]: "RE: Authorization Manager Win 2k3 or XP" 
    Date: Tue, 10 May 2005 15:21:07 -0700

    Thank Marco.

    So you are saying that I could create an invisible dialog using the Wlx
    functions and let this dialog wait for the WLX_WM_SAS meesages and kill all
    the dialogs it knows when one of the messages arrives.

    Regards

    Nick

    "Marco van Nieuwenhoven" wrote:

    > Hi Nick,
    >
    > You can create a dialog which is not visible with the wlx function, place at
    > coordinate 2000,2000 (Or higher when you are lucky ;-). On destroy of that
    > dialog there was a SAS event which should kill a the active dialog. In that
    > case you should end all present dialogs and return from the active gina
    > function. You only need to kill all visibe dialogs and do it as fast as
    > possible.
    >
    > grtx Marco.
    >
    > "Nick" wrote:
    > > Thanks Marco for your reply.
    > >
    > > But is there any work around to make the dialog "robust" instead of touching
    > > the source code of third party libraries.
    > >
    > > As documented in MSDN, WLX_WM_SAS messages are sent to dialogs that Gina
    > > uses. And the SAS type in wParam parameter of WLX_WM_SAS tells what kind of
    > > messages that the Gina dialog is receiving, such as timeouts or user log off.
    > > My question here is that if I handle these messages in dialogs implemented
    > > with normal windows functions, does that make these dialogs equivalent to
    > > dialogs implemented with the Wlx functions?
    > >
    > > Thanks
    > >
    > > Nick
    > >
    > > "Marco van Nieuwenhoven" wrote:
    > >
    > > > Hi Nick,
    > > >
    > > > The Wlx functions take care of the fact that when a SAS event comes that the
    > > > Wlx functions themselves close the active dialog and return the control to
    > > > WinLogon.exe. When having third party modules which pop up normal windows you
    > > > will run into problems. Try to overrule these situations and make your own
    > > > implementations of them using Wlx functions. This will give you a robust Gina
    > > > implementation.
    > > >
    > > > Marco van Nieuwenhoven.
    > > >
    > > > "Nick" wrote:
    > > > > Hi There,
    > > > >
    > > > > In custom GINA, if you want to create a dialog box, you will need to use the
    > > > > functions provided by winlogon, such as WlxMessageBox, WlxDialogBox,
    > > > > WlxDialogBoxIndirect, WlxDialogBoxParam and WlxDialogBoxIndirectParam.
    > > > >
    > > > > According to MSDN:
    > > > >
    > > > > "Winlogon provides a set of dialog support functions for the GINA. The GINA
    > > > > must use these functions instead of their Windows counterparts to ensure that
    > > > > the GINA and Winlogon maintain appropriate control over the dialog boxes.
    > > > > Failure to use the Winlogon versions of these functions could result in
    > > > > unauthorized users gaining access to the system."
    > > > >
    > > > > My question is that when my custom GINA uses third party library (such as
    > > > > PKCS#11) and that thrid party library pops up dialog (such as a dialog asking
    > > > > for finger print) which is not created using those functions, what would be
    > > > > the implication of this?
    > > > >
    > > > > How should I handle this in my custom GINA?
    > > > >
    > > > > Thanks in advance and your help will be greatly appreciated.
    > > > >
    > > > > Regards
    > > > >
    > > > > Nick

  • Next message: Eric Slesar [MS]: "RE: Authorization Manager Win 2k3 or XP"
    Loading