Problem happen when putty trying to connect dropbear

phr phr iamphr at gmail.com
Mon Oct 31 20:00:03 WST 2005


I'm sorry i didn't say it in detail.
 dropbear version: 0.36 (it's really funny right ^^ )
uclinux-0.9.15
linux-2.4.x
nonMMU
putty 0.53b
 i don't have enough space to put dropbear server and key generator on my
embeded system,
so i put key generator first and generate a rsa key file, then rebuild
another image just
only have dropbear server and rsa key file.
 Here are the messages during login into dropbear server.
========================================
TRACE: enter loadhostkeys
TRACE: enter buf_get_priv_key
TRACE: enter rsa_key_free
TRACE: leave rsa_key_free: key == NULL
TRACE: enter buf_get_rsa_priv_key
TRACE: enter buf_get_rsa_pub_key
TRACE: leave buf_get_rsa_pub_key: success
TRACE: leave buf_get_rsa_priv_key
TRACE: leave buf_get_priv_key: done get rsa
TRACE: leave loadhostkeys
Jan 01 00:00:20 Not forking
TRACE: Listen sockets
TRACE: Accept
TRACE: enter session_init
TRACE: In kexinitialise
TRACE: leave kexinitialise
TRACE: enter chaninitialise
TRACE: chaninitialise malloc done
TRACE: chansessinitialise malloc
TRACE: leave session_init
TRACE: enter ident_readln
TRACE: leave ident_readln: return 28
TRACE: remoteident: SSH-2.0-PuTTY-Release-0.53b
TRACE: readrand
TRACE: readrand end
TRACE: enter encrypt_packet()
TRACE: encrypt_packet type is 20
TRACE: enter writemac
TRACE: leave writemac
TRACE: enter enqueue
TRACE: leave enqueue
TRACE: leave encrypt_packet()
TRACE: top of select loop
TRACE: select val = 1
TRACE: enter write_packet
TRACE: empty queue dequeing
TRACE: leave write_packet
TRACE: top of select loop
TRACE: select val = 1
TRACE: enter read_packet
TRACE: enter decrypt_packet
TRACE: leave decrypt_packet
TRACE: leave read_packet
TRACE: enter process_packet
TRACE: process_packet: packet type = 20
TRACE: enter recv_msg_kexinit
TRACE: leave recv_msg_kexinit
TRACE: leave process_packet
TRACE: top of select loop
TRACE: select val = 1
TRACE: enter read_packet
TRACE: enter decrypt_packet
TRACE: leave decrypt_packet
TRACE: leave read_packet
TRACE: enter process_packet
TRACE: process_packet: packet type = 3
TRACE: enter recv_msg_kexdh_init
TRACE: enter send_msg_kexdh_reply
TRACE: enter buf_put_pub_key
TRACE: enter buf_put_rsa_pub_key
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: leave buf_put_rsa_pub_key
TRACE: leave buf_put_pub_key
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: enter buf_put_pub_key
TRACE: enter buf_put_rsa_pub_key
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: leave buf_put_rsa_pub_key
TRACE: leave buf_put_pub_key
TRACE: enter buf_putmpint
TRACE: leave buf_putmpint
TRACE: enter buf_put_rsa_sign
TRACE: leave buf_put_rsa_sign
TRACE: enter encrypt_packet()
TRACE: encrypt_packet type is 31
TRACE: enter writemac
TRACE: leave writemac
TRACE: enter enqueue
TRACE: leave enqueue
TRACE: leave encrypt_packet()
TRACE: leave send_msg_kexdh_reply
TRACE: enter send_msg_newkeys
TRACE: enter encrypt_packet()
TRACE: encrypt_packet type is 21
TRACE: enter writemac
TRACE: leave writemac
TRACE: enter enqueue
TRACE: leave enqueue
TRACE: leave encrypt_packet()
TRACE: leave send_msg_newkeys
TRACE: leave recv_msg_kexdh_init
TRACE: leave process_packet
TRACE: top of select loop
TRACE: select val = 1
TRACE: enter write_packet
TRACE: leave write_packet
TRACE: top of select loop
TRACE: select val = 1
TRACE: enter write_packet
TRACE: empty queue dequeing
TRACE: leave write_packet
TRACE: top of select loop
TRACE: select val = 1
TRACE: enter read_packet
TRACE: enter session_cleanup
TRACE: enter sign_key_free
TRACE: enter rsa_key_free
TRACE: leave rsa_key_free
TRACE: leave sign_key_free
TRACE: enter chancleanup
TRACE: leave chancleanup
TRACE: leave session_cleanup
========================================
 Best Regards,


 2005/10/31, Matt Johnston <matt at ucc.asn.au>:
>
> On Wed, Oct 26, 2005 at 05:40:30PM +0800, phr phr wrote:
> > Hi all,
> > When i trying to connect dropbear server, putty got this message.
> > "Server's host key did not match the signature supplied"
> > Does that mean, my dropbear host key is not correct???
>
> That error tends to indicate that something has gone wrong
> with calculation of the signature by the server. Did the
> Dropbear server print anything interesting in the logs?
> Most likely if the key itself has problems, Dropbear won't
> even start.
>
> What sort of platform are you compiling on? It's plausible
> you could get that error if the crypto libraries are somehow
> producing incorrect output, though it's hard to guess what
> might be wrong without some more details (what sort of
> compiler, platform, libc, etc).
>
> Cheers,
> Matt
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20051031/11faa8e9/attachment.html


More information about the Dropbear mailing list