From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79763 invoked by alias); 18 Jul 2018 23:52:05 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 79368 invoked by uid 89); 18 Jul 2018 23:52:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=BAYES_50,KAM_NUMSUBJECT,MISSING_MID,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*UA:Office, automation, W10, w10 X-HELO: garibaldi.swishmail.com Received: from garibaldi.swishmail.com (HELO garibaldi.swishmail.com) (208.72.56.24) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 18 Jul 2018 23:52:02 +0000 Received: (qmail 58515 invoked by uid 89); 18 Jul 2018 23:52:00 -0000 Received: from unknown (HELO PACLIFF) (cliff.geschke@preciseautomation.com@50.76.241.182) by garibaldi.swishmail.com with ESMTPA; 18 Jul 2018 23:52:00 -0000 From: "Cliff Geschke" To: Subject: sshd service removed by Windows 10 update 1803 Date: Thu, 19 Jul 2018 12:39:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2018-07/txt/msg00174.txt.bz2 Message-ID: <20180719123900.9SnKLMrmSzcO1xUL4spW5Tg2AJ1pldtIq_llRHjuV4o@z> 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 successfully 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 SSHdBroker 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 1062: The service has not been started. The task manager shows sshd is indeed running, and remote ssh clients can log in. So I am ignoring the error. cygrunsrv -Q sshd shows the service is stopped. And W10 computer management shows it is stopped. If you try to start it again, it will fail because the 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 sshd. Not what I want. If you don't specify --user with the --install, W10 will use SYSTEM which does 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 and 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 the service is stopped, everything seems to work okay and my users are happy again. 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