Hi - I'm running into a little bit of a usability problem with dropbear 0.50. The OpenSSH client can connect to the dropbear server running on an embedded ARM platform ( Linux 2.6.17, uLibC, busybox v1.2.0 ), but it takes between 50 seconds and a minute to connect. It doesn't look like a CPU problem as the dropbear process sits at 0% CPU utilization for the majority of this time. Running dropbear in the foreground displays the following
# dropbear -E -F -s [365] Aug 20 09:45:13 Failed reading '/etc/dropbear/dropbear_dss_host_key', disa bling DSS [365] Aug 20 09:45:13 Not backgrounding [366] Aug 20 09:45:28 Child connection from 10.2.3.2:51284 [366] Aug 20 09:46:12 pubkey auth succeeded for 'root' with key md5 <removed> from 10.2.3.2:51284 The client side displays the following > ssh -v [EMAIL PROTECTED] OpenSSH_4.2p1 FreeBSD-20050903, OpenSSL 0.9.7e-p1 25 Oct 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 10.2.3.232 [10.2.3.232] port 22. debug1: Connection established. debug1: identity file /home/ctuffli/.ssh/identity type -1 debug1: identity file /home/ctuffli/.ssh/id_rsa type 1 debug1: identity file /home/ctuffli/.ssh/id_dsa type -1 <hangs here> debug1: Remote protocol version 2.0, remote software version dropbear_0.50 debug1: no match: dropbear_0.50 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.2p1 FreeBSD-20050903 debug1: SSH2_MSG_KEXINIT sent ... debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. Has anyone seen this problem before? Ideas? Thanks! ---chuck
