Could be your ssh client proposing ciphers the SSH server doesn't
understand. This was known issue with communication of ssh client 5+ to ssh
server 4.x and older.
Give it a try and let us know.
http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh-client-connection-reset-by-peer/
On Mon, Mar 30, 2015 at 2:33 PM, Pol Hallen wrote:
> hey all :-)
>
> unfortunately I don't have access to ssh server, I can only see:
>
> Platform: i586-pc-linux-gnu
> Compiled with: liblua-5.2.3 openssl-1.0.1k libpcre-8.35 libpcap-1.6.2
> nmap-libdnet-1.12 ipv6
> Compiled without:
> Available nsock engines: epoll poll select
>
> ssh -vvvl user ip
>
> debug2: kex_parse_kexinit: first_kex_follows 0
> debug2: kex_parse_kexinit: reserved 0
> debug2: mac_setup: setup hmac-sha1
> debug1: kex: server->client 3des-cbc hmac-sha1 none
> debug2: mac_setup: setup hmac-sha1
> debug1: kex: client->server 3des-cbc hmac-sha1 none
> debug2: bits set: 502/1024
> debug1: sending SSH2_MSG_KEXDH_INIT
> debug1: expecting SSH2_MSG_KEXDH_REPLY
> Connection closed by IP
>
> any idea to solve?
>
> Thanks!
>
> Pol
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/551942a6.6080...@fuckaround.org
>
>
