From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd issues on Windows 10 version 1803
Date: Mon, 25 Jun 2018 13:12:00 -0000 [thread overview]
Message-ID: <20180625121009.GA29611@calimero.vinschen.de> (raw)
In-Reply-To: <CAFcD33OUWb2rvHhvkbvW7PP49NMCt_M2Y+erc0_wAYSGvvrYDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]
On Jun 22 11:27, Hiya Z wrote:
> Hello,
>
> 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:
>
> - 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.
>
> - %SystemRoot%\system32\openssh is added to the system PATH.
>
> - a (manual start) service "sshd", displayname="OpenSSH SSH Server",
> imagepath=%SystemRoot%\system32\openssh\sshd.exe, gets created.
>
> 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 start
> 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.
>
> 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 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.
>
> 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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-25 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 20:42 Hiya Z
2018-06-25 13:12 ` Corinna Vinschen [this message]
2018-06-25 18:59 ` Corinna Vinschen
2018-06-25 20:20 ` Corinna Vinschen
2018-06-26 8:16 Hiya Z
2018-06-26 16:03 ` Corinna Vinschen
2018-06-29 6:20 Hiya Z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180625121009.GA29611@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).