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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=VpNNzBZ4PbOQ6VPQhPM7Vne8D2bwjNUEfytunLlPuVtsprroNuM6+
	RWutW50Lsf7kRRXWKDlyPtxCmnVXfGUxZvEkY7AXNA8pUYInf04MC6Sn/AaR3vIx
	f0TCPBjFP8ZVJ1huWD3eQa2OxTker28H4etbYgFXDfJDB5DVr0733k=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=HsihnaQrroiOA9tW8PIDAs3iZn0=; b=FgL9bzyADIAoUlQK2BgTLRyvLlh4
	OKGXGT8+ABnSKiaVALn63IhOOTrQKqwSGM5BvfbCcSCFZbbs4uX7zgJwQioOH24T
	7ISkVYsa6WeordqWoNUFi4vYxVekbchZEJCoW/TGZL9X5iAM/pAIISHptFrDMxit
	f/j6faGJX07rjSk=
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-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=family
X-HELO: mout.kundenserver.de
Date: Mon, 25 Jun 2018 16:24:37 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sshd issues on Windows 10 version 1803
Message-ID: <20180625142437.GN28757@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAFcD33OUWb2rvHhvkbvW7PP49NMCt_M2Y+erc0_wAYSGvvrYDw AT mail DOT gmail DOT com> <20180625121009 DOT GA29611 AT calimero DOT vinschen DOT de> <20180625140817 DOT GM28757 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="9aCKuHbn5v2q3RVc"
Content-Disposition: inline
In-Reply-To: <20180625140817.GM28757@calimero.vinschen.de>
User-Agent: Mutt/1.9.2 (2017-12-15)

--9aCKuHbn5v2q3RVc
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun 25 16:08, Corinna Vinschen wrote:
> On Jun 25 14:10, Corinna Vinschen wrote:
> > On Jun 22 11:27, Hiya Z wrote:
> > > Hello,
> > >=20
> > > Now that Microsoft has bundled OpenSSH for Windows in update 1803 (see
> > > https://blogs.msdn.microsoft.com/commandline/2018/03/07/windows10v180=
3/),
> > > here are some observations and the resulting unfortunate behavior:
> > >=20
> > > -  On a clean vanilla 1803 install, even with Windows Subsystem for L=
inux
> > > (WSL) not installed, there exists a folder %SystemRoot%\system32\open=
ssh
> > > that has native Windows ssh and sshd executables.
> > >=20
> > > -  %SystemRoot%\system32\openssh is added to the system PATH.
> > >=20
> > > -  a (manual start) service "sshd", displayname=3D"OpenSSH SSH Server=
",
> > > imagepath=3D%SystemRoot%\system32\openssh\sshd.exe, gets created.
> > >=20
> > > All of the above have the unfortunate consequence that Cygwin sshd no
> > > longer works reliably on a 1803 install. First, the service name "ssh=
d"
> > > conflicts. This can be worked around by something like "ssh-host-conf=
ig -N
> > > cygwinsshd". Even then, the Cygwin sshd does not always automatically=
 start
> > > upon reboot. The Windows sshd is not configured/running, so there sho=
uld
> > > not be a port conflict. SCM reports timeouts (waiting for cygwinsshd =
to
> > > respond) in the event viewer. A manual "sc start cygwinsshd" works, b=
ut
> > > again, upon the next reboot, the problem is back.
> > >=20
> > > There are other permutations depending on the sequence of install. If=
 I
> > > were to upgrade a Windows 10 1709 node with a working Cygwin sshd, it=
 seems
> > > that the 1803 update detects an existing sshd registry key (which rea=
lly is
> > > Cygwin), does not clobber the registry keys, nor does it install sshd=
.exe
> > > under %SystemRoot%\system32\openssh (though ssh.exe and family get
> > > installed). Even on this node, the Cygwin sshd shows the same issue o=
f not
> > > autostarting reliably upon reboots.

Btw., I can't reproduce this problem.  Cygwin's sshd service always
starts for me at boottime as expected.

Did you check if the log file in /var/log contains any more info?


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--9aCKuHbn5v2q3RVc
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlsw+yUACgkQ9TYGna5E
T6D3gQ/9EvUz5H4Klw1MuspQoSYbovnNrOO5sLBGhegvv0RAvsI4LV9mt8/uIQJY
zwLVmEbNT5YrZCI/oGRj9/b5OQgJnrwTZArddp5u9IrmTlqeVHC8Yp9o5zwV4J2g
gXiYnYSeheWPCGTwi2sIxliZvnRlHYnGN6LffGyCSJi/wu/Tms5Jy3ptyyl0XQrx
/RN23IHgoYT8IuM6ADKv8eOsEcjnhQJ+GVYKbpZMqk+43rHsVK/ovBWFDGVaLSOz
d4fVxCl+B7KW92c73KntcfCmtLXzjudIBMGJOj9A9DgN57Ycf1LvCAtVHUvH0YHN
JDw8gc4VKV6lR1/PUy+HKmbk8sqfmy7B0GZSvNzW/mHYmCBTW3NlpY0hdK6EAr5g
A2OG+1cbr5+Dqs4rwwKkT/e0DZfz5Szhx83r2v4MpZKX1b0RRLhg7ljEZIeaAnle
5KF2OP7dUrDpw29UEYwlqG6rEWxUufUO/8o9p3MpJTlBS7fy4AnCBIvdKVaCG5Wa
f1Q2EizMqU6ei9xIt/NGHDRdG95a0xWqY4GCOlnFc+vPPJgH3aBcT83gwUC7v6Q4
LW3n42W76HahT56sGZrJz/qeNdX+La9PEeCJiXynsF90kOzB0Smql7luapYWmf4g
HDxqrGQ3Jqk1kJI51zP7QQLsK8KDhVifYNtmIYYI+edc+HnT/0Q=
=1wXP
-----END PGP SIGNATURE-----

--9aCKuHbn5v2q3RVc--