DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=pJ6cPSGGN0hSH76s
	2W+NljYlpMcVx+2fO8tSpKBN3bVyCIH/U9JJ2BF1x5Y49kVblzNJZWxeui6+MYUl
	Y64jVZUU8YpLvTWCloVNXFEcp1oGkwwcPVd2SXocY0LGhzigRHHHjCmEgThfD2S6
	ALlbhya55NZotBbXb9UKBBDEFLc=
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
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: cygwin sshd vs Win 10 'built-in' openSSh server
To: cygwin AT cygwin DOT com
References: <CAFKs89Frr_jE8fryf75=3R_YkNO64OiWYJ8ToeFVxLLfxP+=UA AT mail DOT gmail DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <b6da84b8-a157-8ca8-0bc9-42f4e7743ea4@SystematicSw.ab.ca>
Date: Thu, 21 Nov 2019 13:47:08 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAFKs89Frr_jE8fryf75=3R_YkNO64OiWYJ8ToeFVxLLfxP+=UA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2019-11-21 09:07, Evan Cooch wrote:
> I've been using the cygwin sshd as a service under Windows (XP -> 7), for 
> *many* years. However, with the pending deprecatin of Win 7, and the IT guys
> at my institution nagging me to upgrade to Win 10, that raises a question --
> are there relative pros/cons of sticking with cygwin sshd as a service under
> Win 10 (assuming that is still possible), or enabling the openssh server that
> is 'hidden' (relatively speaking) in Win 10 Pro an Enterprise (not so sure
> about Win 10 Home)?
> 
> My preference would be to stick with cygwin (since I'm familiar with it, and
> can tweak things as I need), but I'm uncertain as to how well it would play
> with Win 10, which might be 'happier' if the MS approved openssh approach was
> used.
> 
> Thoughts/opinions?  I have a couple of Win 10 installs in virtual machines, 
> and will try testing both approaches at some point, but wanted to collate 
> some information before that point.

With Cygwin you have documentation, familiarity, prompt support and fixes, and
support of standard cypher suites and key sizes.

What do you know about MS "hidden" ssh server and client, and interop with the
systems to which you want to connect?

What can you expect by way of support from your IT guys and MS?

Some wiki notes are less than informative and may be worrysome:
https://github.com/PowerShell/Win32-OpenSSH/wiki/SSH-remote-sessions-on-Windows
"A remote session opened via password authentication has the user credentials
attached to it and hence is capable of outbound authentication as the user.
A remote session opened via key based authentication does not have associated
user credentials and hence is not capable of outbound authentication as the
user. This is by design and goes by the rules of standard Windows security."
https://github.com/PowerShell/Win32-OpenSSH/wiki/ssh.exe-examples

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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