Peter Stuge wrote: > > libssh2 can't get past key exchange with the (public) server > > dante.u.washington.edu. > > I'm analyzing this now.. It's strange.
libssh2 thinks it has sent KEX, but TCP has not yet gotten an ACK for the client identification string. Gut feeling is that the problem is in TCP on the server end.. Not sure if libssh2 should send KEX before the client identification has been ACKed. //Peter _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
