Re: Questions regarding developing gina.dll under XP
- From: "Philippe C. Martin" <philippe@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 30 Apr 2005 16:18:13 GMT
Hi Christoph,
Apparently, there is no "Local Security Policy" for non-professional XP, and
I do target people with regular XP .... lots of them.
Do you think that means I am stuck with using timers as I will never get
those events ?
Regards,
Philippe
Christoph Wienands wrote:
> Hey Philipe,
>
>> 1) I understand from my reading that I will not get any card_inserted
>> event
>> if the PC is not hooked to a domain, is that true. (since my test PC is
>> not
>> hooked to a domain and that I don't get such event, I use a timer to poll
>> for my card ... seems to work OK)
>
> No idea about that...
>
>> 2) The first dialog box I pop up on boot from WlxDisplaySASNotice (ex:
>> press ctrl-alt-del or insert card) closes right away for a reason I have
>> yet to understand, I then get the next dialog box from WlxLoggedOutSAS.
>> On top of it, since my timer has not yet seen my card, I get the
>> following sequence:
>>
>> a) DLG: "CTRL-ALT-DEL or INSERT CARD" (that closes "by itself")
>> b) DLG "Enter your username, password, domain" (since the timer has not
>> seen
>> the card yet)
>> c) DLG: "Enter your PIN code" (my timer saw the card, tries to end dialog
>> (a), which is closed, for some reason dialog (b) closes and I get the
>> "enter pin dialog I need". Thatlooks very hugly
>
> Depending on how your policy "Interactive Logon: Do not require
> Ctrl-Alt-Delete" is set, you will get the dialog "CTRL-ALT-DEL or INSERT
> CARD" or you won't (maybe that's the reason why you see it flashing
> briefly). You can find that value in "Local Security Policy".
>
>> 3) I understand from my reading that the only way to lock the screen when
>> the logged on user removes his card is to send a screen saver event and
>> to configure the system so the screen saver will require identification
>> to unlock. I send that event from yet another timer, I see the screen
>> saver come up, but if I do not wait a few seconds before touching a key
>> or click the mouse, I do not get the WlxDisplayLockedNotice called. So I
>> have yet to
>> make another hugly piece of code to fix that.
>
> I don't quite understand your problem. When the user removes his keycard
> you should get a SAS event. You can identify the case that the user
> removed the card with the dwSasType parameter. Then you simply return
> WLX_SAS_ACTION_LOCK_WKSTA and the wksta should be locked again.
>
> Christoph
.
- References:
- Questions regarding developing gina.dll under XP
- From: Philippe C. Martin
- Re: Questions regarding developing gina.dll under XP
- From: Christoph Wienands
- Questions regarding developing gina.dll under XP
- Prev by Date: Re: Process information
- Next by Date: Re: Enable or disable devices
- Previous by thread: Re: Questions regarding developing gina.dll under XP
- Next by thread: Not Responding Process
- Index(es):
Relevant Pages
|
