Re: WinHelp on W2003 SP1
- From: "Pavel Lebedinsky [MSFT]" <pavel@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 May 2005 23:44:21 -0700
Note that interactive services are strongly discouraged. If a service
displays UI on the user's desktop, the user can often exploit this
and gain the same privileges as the service account (so called
"shatter" attack).
As a workaround for your problem, you can use CreateProcess
or some other API that doesn't automatically block until the child
process terminates. But ideally you should use a proxy process
running in the user's session to display the UI:
http://support.microsoft.com/default.aspx?scid=kb;en-us;327618
http://support.microsoft.com/default.aspx?scid=kb;en-us;308403
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Rhett Gong [MSFT]" wrote:
> Hello Sue,
> Is the service installed or written by you?
> If it is installed by your as system service, you may need to check the
> "Allow service to interact with desktop" to allow the winhlp32 to display
> in the active desktop.
> "Allow service to interact with desktop" can be found through following
> stesps:
> 1> run services.msc in your run box
> 2> locate your service and click property
> 3> in Log On tabpage, if you log on your service as Local System Account,
> please check the box below.
>
> Please let me know if my answer helps you resolve the problem. If there is
> anything more I can assist you, please feel free to let me know.
.
- Follow-Ups:
- Re: WinHelp on W2003 SP1
- From: SueM
- Re: WinHelp on W2003 SP1
- References:
- WinHelp on W2003 SP1
- From: SueM
- RE: WinHelp on W2003 SP1
- From: Rhett Gong [MSFT]
- WinHelp on W2003 SP1
- Prev by Date: RE: WinHelp on W2003 SP1
- Next by Date: RE: WinHelp on W2003 SP1
- Previous by thread: RE: WinHelp on W2003 SP1
- Next by thread: Re: WinHelp on W2003 SP1
- Index(es):
Relevant Pages
|