X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=VwecJF+OOCC0IUB7+o9YUIyyOqR8O
	ffxT7nuFAz3v+61Bdq4JM5lAN6YHxIdO9n4lsiHbwS6zcHYgHkhLVEdFwVauXAeN
	gmqB2cCIM/cwuT89dy0ls145r7ZnHBSLzVn7/8bMMWZTdEyaMegytpym5FHeNE+s
	+valltyLyI/HYk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; s=default; bh=UTRs7ghAB1ABmsCVg6ndUFlY80c=; b=nD9
	j2zHU+PXGm9sSGjvaYGBswlWUKdFb1M1KnhrrP+nydaD+g2XCECC+8Iu226LPXj6
	h36rORFtWk1A+gNNg1aB4W+Wl++dlrFUusWOdcBwWC09JMEC9Kf1eXrTd2GM/THe
	mG0sl1S3RMfb2uzOWMLTFOJPeClcd/26zv76LrcY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=1.9 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=happier, Home, upgrade, Enterprise
X-HELO: mail-ot1-f48.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:from:date:message-id:subject:to;        bh=v7JIrKwrE0BunhYig2plHJbfck/3eNVYy/vzwHCo3ag=;        b=VDqWHrOnr7dsMjwLLKL21g2DVuVIW3xcM3R7xU1cW8JGx4owgwCezQOMuijCAri6Ns         xloqJc5hboMjpNNft3xn0sp1UfREXp0o/YaM5O2PTMVkkTcxaDtSkJ4BTnE9DjGW5fpD         kn91yYOrRI8cbK4VY+eeC0jikXRDJWKaWJyPpIcMEU0bQYwbDXZH375QJjoiZ9KWX0h8         Wc2VoTm0pDHbRDRs2s1NWkoNll64ymwH2qzQoKaseDtznn0twSdV8lrGBsK9AXtwl+iD         srT5HvYRVKr+jAXHmVqEVMnkkDzlcp7HGYtiiWgowDCQw21XZgSf2/EaJFsYwQCketFy         N9nQ==
MIME-Version: 1.0
From: Evan Cooch <evan DOT cooch AT gmail DOT com>
Date: Thu, 21 Nov 2019 11:07:24 -0500
Message-ID: <CAFKs89Frr_jE8fryf75=3R_YkNO64OiWYJ8ToeFVxLLfxP+=UA@mail.gmail.com>
Subject: cygwin sshd vs Win 10 'built-in' openSSh server
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

Greetings --

Apologies if this should go to another list, but...

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.

Thanks 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