This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Run OpenSSH service with Local System Account

Hi Corinna,

Thank you for the clarification. It is a Microsoft driver testing tool
and it can run automated mode so that it will dismiss the confirmation
dialog boxes automatically in a regular session but it will hang in a
windows service context when those confirmation dialog box pops up.

I figured a workaround. Basically I call the task and scheduler
utility (schtasks.exe) from the testing script running in the service
context to create a task and run it. The task runs the GUI test tool
in the currently  logged on user context and can interact with its
desktop. Whew...  case closed.


On Fri, Nov 21, 2008 at 2:31 AM, Corinna Vinschen
<> wrote:
> On Nov 20 15:37, William Zhang wrote:
>> Hi All,
>> Sorry i hit the send button by mistake before I finished the last
>> mail. This is my
>> full question.
>> I am wondering if there is a way to run the Cygwin OpenSSH service as
>> Local System Account in Windows 2003 and 2008 instead of the
>> cyg_server account created during the setup.   I am using
>> Cygwin+OpenSSH on the Windows test server and I remotely execute
>> automation testing script from a linux box. However the program
> This won't work.  The reason why you can't use the LocalSystem account
> to run sshd (*and* get pubkey authentication) is not a Cygwin
> restriction, but a Windows restriction.  With Windows 2008 this works
> even worse because the "Interact with desktop" has been officially
> deprecated for security reasons.  It's still available in the services
> GUI but it doesn't work as on earlier systems.
> There are probably other workarounds for your problem.  What exactly
> are you testing?  Why do you need interaction with the desktop, even
> though you're doing automated script testing?
> For instance, the official workaround as propagated by Microsoft is to
> start the application by the user account running the desktop session
> and to use IPC mechanisms (named pipes, sockets) to communicate between
> the service and the desktop application.
> Corinna
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader          cygwin AT cygwin DOT com
> Red Hat
> --
> Unsubscribe info:
> Problem reports:
> Documentation:
> FAQ:         

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]