Re: sshd service removed by Windows 10 update 1803
- Date: Thu, 19 Jul 2018 10:34:47 +0600
- From: madhu gupta <m.gupta60@xxxxxxxxx>
- Subject: Re: sshd service removed by Windows 10 update 1803
On Thu, Jul 19, 2018 at 5:51 AM, Cliff Geschke <
> As part of a Windows 10 update 1803 a few days ago, the cygwin sshd
> service was
> removed, keeping my users from accessing my server. I had been
> using sshd for several years and it has survived numerous windows updates.
> Here is what I have done to fix it:
> Disable the following services via W10 computer management.
> OpenSSH Authentication Agent
> SSH Server Broker
> SSH Server Proxy
> I'm not sure all those need to be disabled.
> Run a bash shell as administrator, and reinstall sshd using cygrunsrv
> cygrunsrv --stop sshd
> cygrunsrv --remove sshd
> cygrunsrv --install sshd --path /usr/sbin/sshd.exe --user cyg_server
> cygrunsrv --start sshd
> You will get an error from the start command:
> cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error
> The service has not been started.
> The task manager shows sshd is indeed running, and remote ssh clients can
> in. So I am ignoring the error.
> cygrunsrv -Q sshd shows the service is stopped. And W10 computer
> shows it is stopped. If you try to start it again, it will fail because
> sshd task has a hold on the TCP ports. If you want to stop/restart to edit
> config files, you need to directly kill the sshd task.
> After a system restart, W10 starts the correct sshd again.
> Simply using "cygrunsrv --install sshd" without --path, installs the MS
> Not what I want.
> If you don't specify --user with the --install, W10 will use SYSTEM which
> not have the permissions (SeTcbPrivilege etc) to change to the client
> user. So
> you get seteuid Operation Not Permitted errors when a remote client tries
> fails to login. I discovered this the hard way.
> BTW, I didn't want to start over with ssh-host-config because I didn't
> want to
> risk invalidating my encryption keys and confuse my remote clients.
> Except for the weirdness where computer management and cygrunsrv -Q show
> service is stopped, everything seems to work okay and my users are happy
> Cliff Geschke
> Precise Automation
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple