Hi, i'm having PROXYCOMMAND issues.
I'm trying to connect from our rhel7 servers to external sftp servers via our socks5 server.
-the rhel7 sftp cli +ncat works ( sftp -vvv -o ProxyCommand='ncat -vvv --proxy <proxy server:port> --proxy-type socks5 %h %p' -o'User <user>' -P 22 <external site> )
but the libssh connection don't.
Attatching failing communication capture:
Libssh bails with "read_packet(): Packet len too high (1818845006 6c69626e)" after ss_send_kex: SSH_MSG_KEXINIT sent
(6c69626e is "libn" in ascii)
I've tested last stable libssh and the latest master (27/1), forcing KEX algo and C_S S_C chipers etc. to no avail. Still the same packet response from 2 diffrent external sftp servers. I'm on statically linked OpenSSL_1_1_0-stable (latest commit) and have further tested with openssl 1.1.1 & boringssl with the same result
Our socks5 proxy don't do any ssh interception
libssh "indirect" connections via a external socks5 bridge / virtual NIC & statically linked borinssl works from my windows7 workstation though.
I guess this is an issue with the openssl implementation since it works for the workstation / boringssl implementation or Is there any issue with the PROXYCOMMAND implementation ?