[Jon Abbott]

AddGadget.exe is attached, simply run it using the full path/filename of the gadget.

How does it work
It runs the .gadget file, waits for the security prompt to appear and then clicks the Install button.
To get around the user clicking away, it repeatedly makes the security dialogue the active window until it's been closed.
If the window isn't found after 5 seconds, it will quit.

It's compiled with AutoIt, the complete code is as follows:

AutoItSetOption("TrayIconHide", 1)

If $CmdLine[0]=0 or $CmdLine[1]="/?" Then
	MsgBox(0, "AddGadget", "Usage: AddGadget ""<path>\<.gadget file>""" & @CR & "   eg: AddGadget ""c:\temp\Clock.gadget""")
	Exit
EndIf

Run("rundll32.exe shell32.dll,ShellExec_RunDLL """ & $CmdLine[1] & """")

While WinWait("Install Gadget - Security Warning", "", 5) = 1
	WinActivate("Install Gadget - Security Warning")
	Send("{LEFT} ")
WEnd

Attached File(s)

•  AddGadget.zip (110.97K)
  Number of downloads: 91

[Stanimir Stoyanov]

The application is interesting, but you might want to reconsider the approach to wait for the window and manipulate it. If the window title changes in future builds or users run a localized build of Windows Vista, the script is likely to enter an endless loop even though it will let users 'answer' the security prompt on their own.

[Jon Abbott]

Stanimir Stoyanov, on Aug 10 2006, 11:38 PM, said:

The application is interesting, but you might want to reconsider the approach to wait for the window and manipulate it. If the window title changes in future builds or users run a localized build of Windows Vista, the script is likely to enter an endless loop even though it will let users 'answer' the security prompt on their own.

Sorry, I should have said, it will quit after 5 seconds if it doesn't find the window.

[Sean1337]

I still don't understand how to use this

[ricktendo64]

Thanks works nicely for XP

[AndreasV]

Auto-Clicking security dialogs is a bad idea - why do you think they are there in the first place?

[Karl]

Quote

Auto-Clicking security dialogs is a bad idea - why do you think they are there in the first place?

QFE - this was my first thought, as well.

[Rafael]

This does show how security prompts are insecure. Randomization of the window class/title should be done to ensure automation isn't possible. A better solution would be for Microsoft to implement a SecureWindow class that prevents people from getting a window handle via Win32 API.