X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=ZNS0XL4
	82rjf/tbqlLfCi5tuJy6ItrOslHmxye1rRWgoie9Ql7qVgGImfqUieXoPS7f79SO
	maczR10BwnGyGS6qX+LPK5dfpTvvxj7avstMOIKs0SSsrmQD9ug69R8grSdvHXuq
	xuKTIs/tawzVMEvJGD1XgMAcA76Y14t0XXEg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=GrmhFv31iHXyE
	rTxCbnRK6Dekqc=; b=CcU6zVBDn57kx2NliBgzTa12AyMluANBiC22kFmHNnvwv
	PBkpf+87H+fgMzs1sAGuhhe3D/vsDlJHy/bVC0U3CvCijd9BJ7xkh/jebFZkM2mR
	BtsWShD2UgAob2F4kwo7xWot7KWH8tLing0Usv/fb5otyBjrYYicWty8Hxqxgk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=Cliff, H*c:alternative, agent, services
X-HELO: mail-oi0-f52.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;        bh=QVEPbcf74XatEJOZlhfx35fVrMN6jiLOeh1PMHDrcZ4=;        b=DSUVwMFlw6LabgWuSdy6O3Bd8qkNSInwnD/gVIEN1YmElFjLplSEOsUwO+CDUZHrW7         OdwCq4mDBr82UM7c3Wl5U9ChtBhYmxL83bUp/EUsOhqXyA0gG4Mv4EEnQjEJwL+i89aN         eVCrg99wrtgT4T9uwJOwwmsnXuwuDHmaPo2jYM7d2B9EigjrJ86CvLr7fI284WBFjaC/         ITk6KKH1WDL7Cu7cOtRbUOT7yiJH6YOA//FBurv/Q6rr4Av9lfcc8BtDrgWzOWAzf2Fq         rpMEE3JeMlAj93kyyHN0vR1Im5o2fl9XNnNCcQcoJa8EgRXyAS2YpplHuCgeXWDT3q/I         WbOQ==
MIME-Version: 1.0
In-Reply-To: <5b4fd2ad.1c69fb81.3e7e4.c9cdSMTPIN_ADDED_MISSING@mx.google.com>
References: <5b4fd2ad DOT 1c69fb81 DOT 3e7e4 DOT c9cdSMTPIN_ADDED_MISSING AT mx DOT google DOT com>
From: madhu gupta <m DOT gupta60 AT gmail DOT com>
Date: Thu, 19 Jul 2018 10:34:47 +0600
Message-ID: <CAAAgaWF9cR2TXJEB_86AQ3hrsvwhNZwwgCxs+daC1P+=2uVv=g@mail.gmail.com>
Subject: Re: sshd service removed by Windows 10 update 1803
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

Thanks.

On Thu, Jul 19, 2018 at 5:51 AM, Cliff Geschke <
cliff DOT geschke AT preciseautomation DOT com> wrote:

> 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
>
>

--
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