I've built libssh2 with wincng and have been testing with the CrushFTP
server. All has been working smoothly. In trying to install my software at a
client site, they are attempting to use AWS SFTP service. When performing
the libssh2_session_handshake I am failing with a KEX error.
A log from the server indicates:
Mar 25 13:58:14 pathlabsrv sshd[4988]: fatal: no matching cipher found:
client
aes256-cbc,rijndael-...@lysator.liu.se,aes192-cbc,aes128-cbc,arcfour128,arcfour,3des-cbc
server
aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com
[preauth]
And, indeed, we do not have a matching cipher. I would have expected Windows
cryptography to be generally 'vanilla' and I would have expected Amazon to
support pretty much anything. From my limited experience they seem to have
used Open SSH.
Has anyone encountered this? Can anyone give me guidance?
Wm
-----Original Message-----
From: Daniel Stenberg
Sent: Monday, March 25, 2019 12:37 PM
To: libssh2 development
Subject: RELEASE: libssh2 1.8.2
Hi!
I'm happy to announce a small update to the previous release as we managed
to
get a little hiccup included. Here's 1.8.2!
Get it from https://www.libssh2.org/ as always!
libssh2 1.8.2
This release includes the following bugfixes:
o Fixed the misapplied userauth patch that broke 1.8.1
o moved the MAX size declarations from the public header
This release would not have looked like this without help, code, reports and
advice from friends like these:
Will Cosgrove
(1 contributors)
--
/ daniel.haxx.se
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
