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:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=kKG2Yiy
	1KE+M97xcerKoYEvAK4o/MfLlntrDBiseMxFEMWIMjhnoO/xMNktRa1Z+QxBqCQk
	VyGqT3LGn0DASAYgGkNJSrAqWgE+AlJleo6t45ud06j4K4AoJXfVJ6pQ9UB6KmE6
	kwiC59HWHd2JD/dX5GeWFcXW+Xh2ygy7Vch4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <1582826967147-0.post@n5.nabble.com> <CANV9t=QA+Hp_ofQ+0JYCGRiokDTsKU25cu_HK7KA6=DMi3YNKw@mail.gmail.com> <1582845015610-0.post@n5.nabble.com>
In-Reply-To: <1582845015610-0.post@n5.nabble.com>
From: Bill Stewart <bstewart@iname.com>
Date: Fri, 28 Feb 2020 07:53:24 -0700
Message-ID: <CANV9t=T_Qg4xuh3GeYgXDF7ZCEcbtcm-NfA1OGh=Smq8NXtoAA@mail.gmail.com>
Subject: Re: OpenSSH: SSHD daemon (as SYSTEM) is partially broken
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On Thu, Feb 27, 2020 at 4:10 PM TestUser1 wrote:

So is this expected to work fine in my environment, Windows Server 2016 (OS
> Version 10.0.14393), without the workaround?
>

 I can't reproduce on Windows Server 8.1/Server 2012 R2 or later.

But you can certainly try the workaround.

Bill

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