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=Tt4VMfQPWRz2jAPlo2IeSE9wq7tizN+oOgJIY31WnadU3+/5dyokE
	AIqdbUOB1s7zZoCubFf9uRZRfZVKszd1N/MAInYUqsGhmN9F11b+iQ1BOnkLtI36
	3dcgaCAWIDiP5cgv/uZpfdI2ynrWHe45DSINn8zKkI7QbiiqjIRiZA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 25 Jun 2018 16:08:17 +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: <20180625140817.GM28757@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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="CD/aTaZybdUisKIc"
Content-Disposition: inline
In-Reply-To: <20180625121009.GA29611@calimero.vinschen.de>
User-Agent: Mutt/1.9.2 (2017-12-15)

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

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/windows10v1803/=
),
> > here are some observations and the resulting unfortunate behavior:
> >=20
> > -  On a clean vanilla 1803 install, even with Windows Subsystem for Lin=
ux
> > (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 s=
tart
> > 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 s=
eems
> > that the 1803 update detects an existing sshd registry key (which reall=
y is
> > Cygwin), does not clobber the registry keys, nor does it install sshd.e=
xe
> > 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 minim=
um,
> > the default service name in ssh-host-config should be changed to not
> > collide with Windows "sshd".
>=20
> 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 :(

However, the longer I think about it, the less I see the problem.  You
can run only one sshd service on port 22 anyway.  If you install 1803 on
a machine with Cygwin sshd service installed, the Microsoft service will
not override (which is rather courteous).  If you install a new machine,
Microsoft's sshd gets installed by default (nice), and if you want to
install Cygwin's sshd instead, you can simply remove the MSFT service
beforehand with `cygrunsrv -R sshd' (easy).


Corinna

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

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlsw91AACgkQ9TYGna5E
T6DV3Q//SdVb4xCIevXlfOjHlhF7s9c9g17K8IldBMV9aBA/xHFOUaSPoc2T1eXd
MU9YKnHB6ZVlaqEjDk/fR97Bp4VIsv4O1YxarS5N7v6oZgVxsbqewvY7w7RrQorf
dzxFW3Skf+SbwkiXNyWL3o7F2GAEsMVn7xgYdCW47d/XNb0zn6nI4gw10QZ2eDbK
RupQ2cwGUSO64RIIvvdEYhQrCsum5MDHzkjt4n8FxzIjddBLlTt6M00ahgqqqh/9
EsZcBqMWnc24Qall4oZvRnZmZJsRr/QmY3pP4og7iH/sJjkY0GlVQc42EY8N5874
pnLAf3DfHMwtQRANVto+tw2hrh0O2ISqT8USZ72n1t15pr/dtjmkK0hlz8gXzfHz
VPlIuWfS3ZFXu6Pd75JpZ70KE7yg2UtbZHLyXONNg7mfLwEyViPovkGWAyA+FXid
jSUgFzFNiOh9HJ8luimHxe08W9ay8Fe6wS0SoCPBl72b+G9jtozFE76rR8PYmNJu
F6N5rAqHkKInmmwoFX+IDvkvAjHxrJnxlBOgV4QG1vO98TYlmT1nypgsQtDKgKwq
tinDyEoYwNIk6UP+No93I0jvZuzHdnIoFeysCQRj7goiLBGDkrupiqQKV7UdZacT
psTNSIHBtgoMAAZ76m3Ep9rO8MTnqkEmpM7CzuAk5IfqeA33Mj0=
=Yyyo
-----END PGP SIGNATURE-----

--CD/aTaZybdUisKIc--