SecureCRT -> SSH-2.0-dropbear_0.36

[Matt Johnston]

On Tue, Nov 11, 2008 at 06:56:49PM +0100, Roman Medina-Heigl Hernandez wrote:
> 
> Putty exposes similar behaviour. Summary:
> 2008-11-11 18:51:30	Looking up host "192.168.0.230"
> 2008-11-11 18:51:30	Connecting to 192.168.0.230 port 22
> 2008-11-11 18:51:30	Server version: SSH-2.0-dropbear_0.36
> 2008-11-11 18:51:30	We claim version: SSH-2.0-PuTTY_Release_0.60
> 2008-11-11 18:51:30	Using SSH protocol version 2
> 2008-11-11 18:51:30	Using Diffie-Hellman with standard group "group1"
> 2008-11-11 18:51:30	Doing Diffie-Hellman key exchange with hash SHA-1
> 2008-11-11 18:51:30	Network error: Connection reset by peer
> 
> Detailed logs:

I can't see anything obvious there. The only way to debug it
further really is to get a login to the device somehow and
have a look at what Dropbear is logging when it exits. I
suppose you could try connecting with dbclient (hopefully
it's compatible...), though it's also possible that the
binary on the router is just plain broken (the compiler has
generated incorrect crypto code, etc).

Cheers,
Matt