DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=oUrQPxFItJ8YMw1oJcTv5/h2GzZtDoaYt3y3GGPtyZQ9Pp
	zFG5bYo8Y028RIgc5FsmywmOD2hY/gtcBV2LNJiPTEYX6h9IfiRgh/nQgfAETTIA
	GiaAYvtjhQSTEiMoiTVol12+Dcedx6aPW2CNIojIYcedX/vSbn03p3VFM2KT0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 27 Feb 2020 16:10:15 -0700 (MST)
From: TestUser1 <pkoshar@compunetix.com>
To: cygwin@cygwin.com
Message-ID: <1582845015610-0.post@n5.nabble.com>
In-Reply-To: <CANV9t=QA+Hp_ofQ+0JYCGRiokDTsKU25cu_HK7KA6=DMi3YNKw@mail.gmail.com>
References: <1582826967147-0.post@n5.nabble.com> <CANV9t=QA+Hp_ofQ+0JYCGRiokDTsKU25cu_HK7KA6=DMi3YNKw@mail.gmail.com>
Subject: Re: OpenSSH: SSHD daemon (as SYSTEM) is partially broken
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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

Thanks!


--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

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