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=ZOZf9iimC6h0U2sNq16YdmXuiDUscUkOVFACIZ9EKrMeb1sPVBDnx
	xilH6G+0ixUirgffyM8DpkEjzGfii8DO1QhRFTUMYZ+0pnbjREnlGka2SgWOqmd+
	DFnYP0m6BbXq1kj3Wp+a8EdY8yOkwLUA2qdC1bVflHbHsybasT0LqY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 25 Jun 2018 14:10:09 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd issues on Windows 10 version 1803
Message-ID: <20180625121009.GA29611@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAFcD33OUWb2rvHhvkbvW7PP49NMCt_M2Y+erc0_wAYSGvvrYDw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo"
Content-Disposition: inline
In-Reply-To: <CAFcD33OUWb2rvHhvkbvW7PP49NMCt_M2Y+erc0_wAYSGvvrYDw@mail.gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)

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

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/windows10v1803/),
> here are some observations and the resulting unfortunate behavior:
>=20
> -  On a clean vanilla 1803 install, even with Windows Subsystem for Linux
> (WSL) not installed, there exists a folder %SystemRoot%\system32\openssh
> 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 "sshd"
> conflicts. This can be worked around by something like "ssh-host-config -N
> cygwinsshd". Even then, the Cygwin sshd does not always automatically sta=
rt
> upon reboot. The Windows sshd is not configured/running, so there should
> not be a port conflict. SCM reports timeouts (waiting for cygwinsshd to
> respond) in the event viewer. A manual "sc start cygwinsshd" works, but
> 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 see=
ms
> that the 1803 update detects an existing sshd registry key (which really =
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 of not
> autostarting reliably upon reboots.
>=20
> I am not sure what Cygwin can do... but reporting this issue to see if
> Cygwin sshd can be fixed to autostart reliably upon reboots. As a minimum,
> the default service name in ssh-host-config should be changed to not
> collide with Windows "sshd".

There's also the problem that %SystemRoot%\System32\OpenSSH is now in
%Path% by default.  Very nice of MIcrosoft to just overload the service
name used by Cygwin for ages :(


Corinna

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

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlsw26EACgkQ9TYGna5E
T6D9aQ//T1vkXA/MnO2TagqCn/zzVSjl0bPu+d1rhmfWQYTXHXPiQeS534gOX1Ye
P585OTKxpIJ/za7CGLma2mfgPj+N0j7rHguDnyMNRpUhrIhGDSMx9jl5iCrnh6JX
8yEQeAGViFUFssFwd33ydmcd8AG23376fEhzARD+Ld9h2UM++3JrYMXxiwU+lf4H
WbsKetKP+5Npq+iNLCboQikfiRgVv5nV71k9g6ZQ3QSwFpwljm2wIa6qosNP5KuO
Pba1mXK6Cl47fqOTAHEyvy3skwMI5Wmm4KdFOpkM48oO7N4mAB9Ey3qc2bwfcr2B
ZF79Z8SEnM7F+TvRGAunj9Ln0x4aTZkGph1DVifgioEc2Kra0h8ZGxO9Omv9FStj
ersexrz2nClnvUOykFylsTC7UIxv0D4CKrDBPXBaBpZu3ZsVz0T6MIt69lqZoEb0
+LUf+Hvy0A/scUBFeplq5Ahf3h/ofv++jXF/eIuUD1ieX3D2lMItVDsvukv9U7Cq
RZwDk9Pdf7XwoRaSGOkJG3laC3tJf1EeKQ9gppWioWeyajFvj8ZAnig8r/SP+Lxu
MPsappZukgmM2KiD+VvfKMdrt60mUhNj54ab6dW5JhOaRqGG7AKy8F4J2ZtbxiqC
sHVPLHScBKlCn1ZLhjVR+ZJ6tPQoF3cVNNdKdBN77BggQ3C+KkM=
=xRoq
-----END PGP SIGNATURE-----

--envbJBWh7q8WU6mo--