DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=fgS
	+hgE4digx7kzs+/ut47TsqZpxLVzoCGKQ/Ji6NZ8SKdlcBGaZgeyrmiUSRoEkqG7
	fkAA8Mw5/5sGfDcWVU7Zm02BRxQe7dYjq8Iw3aezI8ksvVjvo/k3o6uiPRRshtqG
	eKSLs2P6Mn2oIl5AUta9pnV1/09L28Ca6yybj5cQ=
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
To: cygwin AT cygwin DOT com
From: Evan Cooch <evan DOT cooch AT gmail DOT com>
Subject: installing sshd | Win 10 1909 build
Message-ID: <79ab161a-5e1d-e6b2-f46c-275ce7dd719b@gmail.com>
Date: Thu, 26 Dec 2019 15:24:17 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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