public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Evan Cooch <evan.cooch@gmail.com>
To: cygwin@cygwin.com
Subject: installing sshd | Win 10 1909 build
Date: Thu, 26 Dec 2019 21:05:00 -0000	[thread overview]
Message-ID: <79ab161a-5e1d-e6b2-f46c-275ce7dd719b@gmail.com> (raw)

Greetings --

I (and several colleagues) have been using the Cygwin sshd for many 
years (Win XP on...). Has worked perfectly.

However, with the demise of Win 7, several of us have started the 
process of 'upgrading' (in some fashion) to Win 10. For people running 
Cygwin sshd under Win 7, who do an in-place upgrade to Win 10, things 
seem to be OK -- i.e., Win 10 leaves Cygwin sshd alone.

However, I received an email from a colleague who said he had no host of 
problems trying to install Cygwin sshd on a brand new Win 10 system, 
1909 build. It seems that Win 10 has its own sshd, and there is a 
conflict of some sort between Win 10 (which 'wants' to use its own 
sshd), and attempts to use Cygwin.

Since this exercise (of installing to a brand new Win 10 machine) is 
something I'll likely be doing myself in the near future, was wondering 
if there was a canonical set of instructions on how to install Cygqwin, 
using Cygwin sshd as a service, on a Win 10 1909 platform? I've read a 
variety of posts on the matter -- spome suggest renaming the Cygwin sshd 
to something, others talk about registry hacks to not let Win 10 default 
to its own sshd, and so on.

So, is there a 'tried and true, officially sanctioned' way to get Cygin 
sshd running as a service under the latest build of Windows 10, if you 
working with a clean, new install of Windows?

Thanks much in advance...

--
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-12-26 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26 21:05 Evan Cooch [this message]
2019-12-26 21:13 ` Andrey Repin
2019-12-26 23:03   ` Evan Cooch
2019-12-26 23:53     ` Marco Atzeri
2019-12-27  2:29       ` Evan Cooch
2019-12-27  7:20         ` Marco Atzeri
2019-12-27 18:20         ` Andrey Repin

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=79ab161a-5e1d-e6b2-f46c-275ce7dd719b@gmail.com \
    --to=evan.cooch@gmail.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).