OpenSSH_6.2p2, OpenSSL 1.0.1e 11 Feb 2013
debug1: Connecting to 10.0.2.1 [10.0.2.1] port 223.
debug1: Connection established.
debug1: identity file /home/Dimul/.ssh/id_rsa type 1
debug1: identity file /home/Dimul/.ssh/id_rsa-cert type -1
debug1: identity file /home/Dimul/.ssh/id_dsa type -1
debug1: identity file /home/Dimul/.ssh/id_dsa-cert type -1
debug1: identity file /home/Dimul/.ssh/id_ecdsa type -1
debug1: identity file /home/Dimul/.ssh/id_ecdsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version dropbear_2013.56
debug1: no match: dropbear_2013.56
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
Connection closed by 10.0.2.1
Additional INFO
Quote:
Router Model Dlink-DIR600 rev b
Firmware Version DD-WRT v24-sp2 (03/25/13) std - build 21061
Kernel Version Linux 3.2.41-svn21039 #101 Mon Mar 25 10:30:36 CET 2013 mips
CPU Model Ralink RT3350 id:1 rev:2
CPU Clock320 MHz
For the time being, do NOT enter the public key into the router’s authorized key field, or even make the private key available to the SSH client. Only use a username/password, and make sure it’s the password from the GUI. I have no problem accessing a dd-wrt SSHD server using this method. Just avoid all public/private key configuration options until you can at least get in w/ username/password.
Posted: Mon May 20, 2013 13:50 Post subject: Seriously
Seriously, guys?!?!?
No body knows how the */#$ to make SSH work on DDWRT ???
Someone, please can answer the question... HOW THE HELL TO MAKE SSH WORK WITH DDWRT AND CYGWIN ??????????????????????????????????????????????
And what the heck these line mean
Quote:
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version dropbear_2013.56
debug1: no match: dropbear_2013.56
The reason I asked is that it appeared from the log that the connection might still be accessing the keys (perhaps because it saw them), so I wanted them removed, completely.
I have no idea what you may or may not have tried. We get everyone here, from those who are near experts, to those who don't even know what a router is, and everything in-between. I have NO CLUE what you're knowledge level is, and therefore what assumptions to make. Ppl make dumb mistakes all the time. And if we always assumed they didn't/wouldn’t, half the problems would remain unsolved. IOW, I have to assume the worst until proven otherwise.
Back to our story….
It appears that others have had a similar problem w/ that build.
That happens from time to time. A regression is introduced. Don't assume the latest is necessarily the greatest. Try an earlier build.
Of course. I undnerstand. SOrry for that... I was just frustrated of tries and fails... You are totally right...
you are telling that now keys at all should be present... but when I telent to router, under .ssh folder I get some files, obviously with some keys, even when only login with passwrod is enabled
Posted: Mon May 20, 2013 16:52 Post subject: Got that topic after
Your link, yeap... saw that topic already afrter I posted... yesterday I could find anything useful... but today magically things came out... thank you anyway!!
Looks like I will switch to build v20675 as recommended, it was told that this one is more stable than others