public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Hartland <killing@multiplay.co.uk>
To: cygwin@cygwin.com
Subject: Re: HEADSUP: SSHD service rename
Date: Mon, 28 Jan 2019 09:03:00 -0000	[thread overview]
Message-ID: <ecd37390-01e9-c65f-378d-8e800326e1c2@multiplay.co.uk> (raw)
In-Reply-To: <20190128090013.GL3912@calimero.vinschen.de>

On 28/01/2019 09:00, Corinna Vinschen wrote:
> Since Microsoft decided to name their own sshd service "sshd", too, we
> don't have much choice than to rename our service after 16+ years.
>
> https://github.com/PowerShell/Win32-OpenSSH/issues/1331
>
> My patch has been accepted upstream so starting with OpenSSH 8.0, newly
> installed Cygwin sshd services will be called "cygsshd" by default,
> unless Microsoft renames their service yet :}
>
> Of course, systems with already installed Cygwin sshd service will keep
> the service name, even after an update to OpenSSH 8.0.
>
> As some people (including myself) already experienced, an update of your
> W10 system to 1809 may break your sshd service.  The OS update
> apparently overwrites an existing sshd service with its own sshd service
> without asking.  You can just remove the Windows sshd with
>
>    $ cygrunsrv -R sshd
>
> and reinstall Cygwin sshd, or you reinstall Cygwin sshd under another name:
>
>    $ ssh-host-config -n cygsshd   (pre OpenSSH 8.0)
>    $ ssh-host-config              (OpenSSH 8.0 or later)
>
>
> Sorry for the hassle,
> Corinna
Thanks for the heads up its a real pain MS did that, caused me issues a 
few times.

Also watch out for broken firewall rules after this change.

     Regards
     Steve

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

  reply	other threads:[~2019-01-28  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  9:00 Corinna Vinschen
2019-01-28  9:03 ` Steven Hartland [this message]
2019-01-28  9:07   ` Corinna Vinschen
2019-04-22 21:29 ` JZeman
2019-04-23  8:45   ` Corinna Vinschen

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=ecd37390-01e9-c65f-378d-8e800326e1c2@multiplay.co.uk \
    --to=killing@multiplay.co.uk \
    --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).