From: "Nick Popoff" <nick@nickpopoff.net>
To: <cygwin@cygwin.com>
Subject: Problem upgrading from 3.2 to 3.3.1
Date: Sun, 7 Nov 2021 18:58:33 -0500 [thread overview]
Message-ID: <004701d7d433$5f9415c0$1ebc4140$@nickpopoff.net> (raw)
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?
==================
Now I Am having severe problem with 'ssh'. A simple login command like:
Ssh nick@....com <mailto:nick@....com>
Results in the following response:
C:/cygwin64/home/Nick> ssh host.com
Unable to negotiate with <IP> port 22: no matching key exchange method
found. Their offer:
gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,diffie-hellman-group-exchange-sha1,
diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
This is a fresh install of Cygwin on a clean Windows 11. I went back to 3.2
for now as I cannot work with 3.3.1.
Nick
next reply other threads:[~2021-11-07 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 23:58 Nick Popoff [this message]
2021-11-08 5:04 ` Problem with OpenSSH Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2021-11-07 23:44 Problem upgrading from 3.2 to 3.3.1 Nick Popoff
2021-11-08 4:11 ` Takashi Yano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004701d7d433$5f9415c0$1ebc4140$@nickpopoff.net' \
--to=nick@nickpopoff.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).