Am 12.02.17 um 02:19 schrieb Peter Stuge:
> Wesley Witt wrote:
>> Is there some configuration requirement for the host or client?
> Not other than that client and server must be able to agree on
> encryption algorithms.
>
> Enable debugging on the server or tracing in libssh2 and find out
> why kex is failing. We don't know.
Yes, this is probably caused by OpenSSH requiring some modern algorithm
which libssh2 on Windows using WinCNG does not support.
WinCNG does not support AES in CTR or GCM mode yet, but CTR mode is in
the works, see:
https://github.com/libssh2/libssh2/pull/173
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2017-02-12