X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DCBB1385843F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1636344762;
	bh=jG1VJb2QOV2/FNPLYULp4ht4wdoPzT2NoRhe2HYvD9w=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=VGpX1MLO76/ylQ5iV7Sv6+jVABdf85TngBPyukBVqYVOI0SOXB30AgWVr5gmmpvSa
	 HshJ/tCU63hR8QGd0N5fEZlHK2vVlqAaeqjrg/WPrgLUUmvJD6AkHPvuot7cPQbjLy
	 UJSYKwtabH0FJXYpu8m8mB4kKrEQ22xJxZhHZG9E=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 091FA3858401
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 1A84BcME014907
X-Nifty-SrcIP: [110.4.221.123]
Date: Mon, 8 Nov 2021 13:11:49 +0900
To: cygwin@cygwin.com
Subject: Re: Problem upgrading from 3.2 to 3.3.1
Message-Id: <20211108131149.7c5e1caba54ee870ad73546b@nifty.ne.jp>
In-Reply-To: <003a01d7d431$67f7fb70$37e7f250$@nickpopoff.net>
References: <003a01d7d431$67f7fb70$37e7f250$@nickpopoff.net>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin@cygwin.com>
Reply-To: Takashi Yano <takashi.yano@nifty.ne.jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Sun, 7 Nov 2021 18:44:28 -0500
"Nick Popoff" wrote:
> In other words, the 3.3.1 ssh.exe does not accept legacy kex algorithms at
> all, no matter what.  I no longer can log in to Solaris.  For example, it
> DOES NOT accept the following:
> 
> C:/cygwin64/home/Nick> ssh.exe -o KexAlgorithms=+diffie-hellman-group14-sha1
> nick@host.com
> 
> Unable to negotiate with 50.248.140.9 port 22: no matching host key type
> found. Their offer: ssh-rsa,ssh-dss
> 
> Version 3.2 had no problem with legacy algorithms.  Can somebody explain as
> to what is going on here.  Is it a bug?  Or a deliberate break of
> compatibility?

I think this is not due to upgrading cygwin, but due to upgrading
OpenSSH to 8.8p1.

As release note of OpenSSH 8.8p1 says, adding following lines to
~/.ssh/config will solve the issue.

Host *
	HostkeyAlgorithms +ssh-rsa
	PubkeyAcceptedAlgorithms +ssh-rsa

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

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