DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 5981uFIM4005446
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org ED3213858CDA
MIME-Version: 1.0
Date: Tue, 7 Oct 2025 21:55:04 -0400
Message-ID: <CAGQhOhiES-D2zRWJEqw9dHOY4=V=+G-M9oAD2pNZjejeLHOSUg@mail.gmail.com>
Subject: Having issues with newly Cygwin version 3.0 and later..
To: cygwin AT cygwin DOT com
From: James Brown via Cygwin <cygwin AT cygwin DOT com>
Reply-To: James Brown <sacfalcfan AT gmail DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Thanks in advance for any help you can give.  I have 32 bit versions of
cygwin versions 1.7 and 2.4 running on windows 2016 servers.  They work
fine whether it's username/password or sshkeys.  The Linux servers using
cygwin are able to reach our windows and DFS shares without issue.
However, we have installed version 3.5.5 and 3.6 on a windows 2016 server
(3.5) and a windows 2022 server (3.6).  When we use username and password
in our ssh connections everything works fine.  However, when we use an
sshkeys we get permission denied.  When we troubleshooted with Microsoft
they stated the issue was the requests from the linux servers were sending
zero credentials.  We did find some information on cygwin's page about a
change in how credentials were being handled starting with Version 3.  Any
idea how we can get those credentials over to a windows server using
cygwin?

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple